For the complete documentation index, see llms.txt. This page is also available as Markdown.

eth_getTransactionReceipt - Tempo

Example code for the eth_getTransactionReceipt JSON-RPC method. Complete guide on how to use eth_getTransactionReceipt JSON-RPC in GetBlock Web3 documentation.

Returns the receipt for a transaction, including execution status, gas used, and emitted logs. With Tempo's deterministic finality, a receipt's existence implies finality — no re-org-induced disappearance.

Parameters

Parameter
Type
Required
Description

transactionHash

string

Yes

32-byte hash of the transaction

Request Example

curl --location --request POST 'https://go.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "eth_getTransactionReceipt",
    "params": [
        "0x88df016429689c079f3b2f6ad39fa052532c56795b733da78a91ebe6a713944b"
    ],
    "id": "getblock.io"
}'

Response Example

{
    "jsonrpc": "2.0",
    "id": "getblock.io",
    "result": {
        "blockHash": "0x6baa8fa86b9a7e5d3f1c8a4b6e9d2f5a8c3e7b1d4f9a6c2e5b8d3f7a1c4e9b2d",
        "blockNumber": "0x9c40",
        "contractAddress": null,
        "cumulativeGasUsed": "0x12345",
        "effectiveGasPrice": "0x0",
        "from": "0xd85498dbeaeb1df24be52eed4f52eac2fbd56245",
        "gasUsed": "0x12345",
        "logs": [],
        "logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
        "status": "0x1",
        "to": "0x9e7c5e3e3a3b8e1aa0e2d4c7f9d4b0c8b8d5f1a2",
        "transactionHash": "0x88df016429689c079f3b2f6ad39fa052532c56795b733da78a91ebe6a713944b",
        "transactionIndex": "0x0",
        "type": "0x2"
    }
}

Response Parameters

Field
Type
Description

result.status

string

0x1 for success, 0x0 for revert

result.gasUsed

string

Gas used by this transaction (hex)

result.effectiveGasPrice

string

Effective gas price paid in TIP-20 fee units (hex)

result.logs

array

Logs emitted by the transaction — primarily TIP-20 Transfer events for payment flows

result.contractAddress

string | null

Deployed contract address if this was a contract creation

Use Cases

  • Confirming payment success or failure after broadcast

  • Reading TIP-20 Transfer events from receipt logs

  • Computing actual fee cost for accounting

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid <ACCESS-TOKEN>

-32602

Invalid params

Request parameters are missing or malformed

429

Too Many Requests

Rate limit exceeded for your plan

SDK Integration

Last updated

Was this helpful?