eth_getTransactionByHash on Sei
Fetches a transaction's full details (from, to, value, input, gas) by its hash. Returns null if the transaction is unknown or still pending propagation.
Null covers both 'unknown' and 'still propagating', so treat it as 'not yet' and retry rather than 'never'. The blockNumber field stays null until the tx is mined — the cleanest pending-vs-mined check.
Sei endpoint (public — no key)
https://rpc.nodeflare.app/sei/publicMethod
eth_getTransactionByHash
Cost
2 CU
Chain ID
1329
Block time
~0.4 s
Finality
~0.4 s (single-block finality)
Transactions on Sei
Sei executes transactions in parallel (optimistic parallelization), which is why throughput stays high under load. Receipts land within a second of submission.
Parameters
[txHash]cURL
curl https://rpc.nodeflare.app/sei/public \
-X POST \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_getTransactionByHash","params":["0x0000000000000000000000000000000000000000000000000000000000000000"],"id":1}'ethers.js
import { ethers } from 'ethers';
const provider = new ethers.JsonRpcProvider(
'https://rpc.nodeflare.app/sei/public'
);
const result = await provider.send('eth_getTransactionByHash', ["0x0000000000000000000000000000000000000000000000000000000000000000"]);Try it live
Runs the example above against the public Sei endpoint — straight from your browser.
eth_getTransactionByHash on Sei — FAQ
How do I call eth_getTransactionByHash on Sei?
POST a JSON-RPC 2.0 request with "method": "eth_getTransactionByHash" to NodeFlare's Sei endpoint at https://rpc.nodeflare.app/sei/public. No API key is required for the public endpoint.
What does eth_getTransactionByHash cost on the free tier?
eth_getTransactionByHash is weighted at 2 compute units per call. The free tier includes 2,000,000 CU/month, so that is roughly 1,000,000 eth_getTransactionByHash calls per month — no credit card.
Is eth_getTransactionByHash available on the public Sei endpoint?
Yes. eth_getTransactionByHash works on the public Sei endpoint (https://rpc.nodeflare.app/sei/public) with no API key, rate-limited per IP. A free key adds higher limits and a dedicated path.
Anything Sei-specific to know when using eth_getTransactionByHash?
Sei executes transactions in parallel (optimistic parallelization), which is why throughput stays high under load. Receipts land within a second of submission.
Call eth_getTransactionByHash on Sei with a free key
2,000,000 compute units/month, heavy methods unlocked, every chain included. No credit card.
Get your free API key →eth_getTransactionByHash on other chains