eth_getTransactionReceipt

Returns the receipt of a transaction by transaction hash.

Ethereum specification · All supported methods

Parameters

Parameters are positional, in the order below.

Parameter	Type	Required	Description
Transaction hash	32-byte hash	Yes	Hash of the transaction.

Return value

A receipt object, or null when a receipt is not available.

The returned object includes these fields:

Field	Type	Description
type	Hexadecimal quantity	Transaction type as a hexadecimal quantity.
transactionHash	32-byte hash	Hash of the transaction.
transactionIndex	Hexadecimal quantity	Position of the transaction within its block.
blockHash	32-byte hash	Hash of the containing block; null for a pending transaction.
blockNumber	Hexadecimal quantity	Number of the containing block; null for a pending transaction.
from	20-byte address	Sender address.
to	20-byte address or null	Address of the receiver or null in a contract creation transaction.
cumulativeGasUsed	Hexadecimal quantity	The sum of gas used by this transaction and all preceding transactions in the same block.
gasUsed	Hexadecimal quantity	The amount of gas used for this specific transaction alone.
blobGasUsed	Hexadecimal quantity	The amount of blob gas used for this specific transaction. Only specified for blob transactions as defined by EIP-4844.
contractAddress	20-byte address or null	The contract address created, if the transaction was a contract creation, otherwise null.
logs	Array of log objects	Event logs emitted by the transaction.
logsBloom	256-byte bloom filter	Bloom filter summarizing log addresses and topics.
root	32-byte hash	The post-transaction state root. Only specified for transactions included before the Byzantium upgrade.
status	Hexadecimal quantity	Either 1 (success) or 0 (failure). Only specified for transactions included after the Byzantium upgrade.
effectiveGasPrice	Hexadecimal quantity	The actual value per gas deducted from the sender's account. Before EIP-1559, this is equal to the transaction's gas price. After, it is equal to baseFeePerGas + min(maxFeePerGas - baseFeePerGas, maxPriorityFeePerGas).
blobGasPrice	Hexadecimal quantity	The actual value per gas deducted from the sender's account for blob gas. Only specified for blob transactions as defined by EIP-4844.

Example

Replace <gateway-url> with your gateway base URL and <service-url> with the chain’s service path, such as service/ethereum.

curl -X POST "<gateway-url>/<service-url>" \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_getTransactionReceipt","params":["0x504ce587a65bdbdb6414a0c6c16d86a04dd79bfcc4f2950eec9634b30ce5370f"]}'

Illustrative response; values depend on the selected network and request:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "blockHash": "0xe7212a92cfb9b06addc80dec2a0dfae9ea94fd344efeb157c41e12994fcad60a",
    "blockNumber": "0x50",
    "contractAddress": null,
    "cumulativeGasUsed": "0x5208",
    "from": "0x627306090abab3a6e1400e9345bc60c78a8bef57",
    "gasUsed": "0x5208",
    "blobGasUsed": "0x20000",
    "effectiveGasPrice": "0x1",
    "blobGasPrice": "0x3",
    "logs": [],
    "logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
    "status": "0x1",
    "to": "0xf17f52151ebef6c7334fad080c5704d77216b732",
    "transactionHash": "0xc00e97af59c6f88de163306935f7682af1a34c67245e414537d02e422815efc3",
    "transactionIndex": "0x0"
  }
}

Direct behavior

Requests for older chain data are automatically routed to providers with full chain history. This covers blocks, transactions, receipts, and logs independently of historical account state.

The gateway uses the block’s age when known. If the age is unknown, it starts with a full-history provider. A missing result from a provider without the required history is not accepted as proof that the data does not exist.

Transactions and receipts can become visible at different times across providers. A successful lookup does not itself guarantee finality. See consistency boundaries.

For providers

Support the required recent chain-history service. Advertise full chain history only when all included method families and lookup indexes work back to genesis.

See provider qualification for checks and continued eligibility.