Ethereum method

eth_getTransactionReceipt

Returns the receipt for a mined transaction, including its logs and status.

cheapCheap for a provider to serve — no state is read, or one key is.Primary specification

How each provider handles it

Provider support for eth_getTransactionReceipt on Ethereum
Provider	Status	Success	Median	Worst p95	Incidents	Samples
1RPConerpc	Failing	0.0%	—	—	none	24
Blast API	Supported	100.0%	78 ms	124 ms	none	46
Cloudflare	Failing	0.0%	—	—	none	46
dRPC	Supported	100.0%	57 ms	358 ms	none	48
Merkle	Failing	0.0%	—	—	none	23
MEV Blocker	Supported	100.0%	74 ms	729 ms	none	47
NodeReal	Supported	100.0%	58 ms	139 ms	none	48
PublicNode	Supported	100.0%	39 ms	573 ms	none	48
Tenderly	Supported	100.0%	23 ms	51 ms	none	48

Success excludes calls the provider does not implement — an optional method a provider declines to offer is a capability fact, not a failure, and is never scored as one.

Over time

Median latency per minute. Gaps are periods with no measurement, drawn as gaps rather than joined across — a line through missing data invents a measurement that was never taken.

Logarithmic scale — each gridline is ten times the one below it. Click a provider in the legend to hide it. 3 providers are not plotted: they returned no successful response in this window, so they have no latency.

What it does

The receipt is how you learn what a transaction did: whether it succeeded, how much gas it used, and which events it emitted. It exists only once the transaction is mined.

Polling this endpoint is how nearly every application waits for a confirmation, which makes it one of the most frequently called methods in production.

Parameters

transactionHashDATA, 32 bytesrequired: The transaction hash.

Returns

Object — the receipt, or null if the transaction is unknown or still pending.

Try it

Runnable as written, against a keyless public endpoint. Nothing here needs an API key.

Request

curl -s https://ethereum-rpc.publicnode.com \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_getTransactionReceipt","params":["0x85d995eba9763907fdf35cd2034144dd9d53ce32cbec21349d4b12823c6860c5"],"id":1}'

As JSON-RPC

{
  "jsonrpc": "2.0",
  "method": "eth_getTransactionReceipt",
  "params": ["0x85d995eba9763907fdf35cd2034144dd9d53ce32cbec21349d4b12823c6860c5"],
  "id": 1
}

Response

{
  "id": 1,
  "jsonrpc": "2.0",
  "result": {
    "transactionHash": "0x85d995eba9763907fdf35cd2034144dd9d53ce32cbec21349d4b12823c6860c5",
    "blockNumber": "0x14a2f3b",
    "status": "0x1",
    "gasUsed": "0x5208",
    "logs": []
  }
}

Things that bite

status is 0x1 for success and 0x0 for a reverted transaction. A reverted transaction still has a receipt and still consumed gas.
null means unknown to this node — pending, dropped, or simply not indexed here. It does not mean the transaction failed.

Why it is measured

The hash is discovered from a block observed moments earlier rather than hard-coded, so the parameter is always a real, recent transaction and never a stale constant that some providers have pruned.

Called every 300 seconds per endpoint, with jitter so the fleet does not hit a provider in lockstep.

1h window · generated 2026-10-08 21:27:39 UTC · 9 providers