eth_getTransactionByHash - Tempo

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

Returns transaction details by transaction hash. Standard EVM transactions return the usual fields; Tempo Transactions (type 0x54) include additional Tempo-specific fields, such as memo and fee-payer data.

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_getTransactionByHash",
    "params": [
        "0x88df016429689c079f3b2f6ad39fa052532c56795b733da78a91ebe6a713944b"
    ],
    "id": "getblock.io"
}'

Response Example

{
    "jsonrpc": "2.0",
    "id": "getblock.io",
    "result": {
        "blockHash": "0x6baa8fa86b9a7e5d3f1c8a4b6e9d2f5a8c3e7b1d4f9a6c2e5b8d3f7a1c4e9b2d",
        "blockNumber": "0x9c40",
        "from": "0xd85498dbeaeb1df24be52eed4f52eac2fbd56245",
        "gas": "0x5208",
        "gasPrice": "0x0",
        "maxFeePerGas": "0x0",
        "maxPriorityFeePerGas": "0x0",
        "hash": "0x88df016429689c079f3b2f6ad39fa052532c56795b733da78a91ebe6a713944b",
        "input": "0xa9059cbb000000000000000000000000d85498dbeaeb1df24be52eed4f52eac2fbd5624500000000000000000000000000000000000000000000000000000000000003e8",
        "nonce": "0x42",
        "to": "0x4242424242424242424242424242424242424242",
        "transactionIndex": "0x0",
        "value": "0x0",
        "type": "0x2",
        "chainId": "0x1079",
        "v": "0x0",
        "r": "0x4f3a1c...",
        "s": "0x6c8d2b..."
    }
}

Response Parameters

Field
Type
Description

result.blockHash

string

null

result.from

string

Sender address

result.to

string

null

result.input

string

Calldata. For TIP-20 transfers, this encodes the transfer(recipient, amount) call

result.value

string

Effectively unused on Tempo — payments use TIP-20 transfer calls in calldata, not the native value field

result.type

string

Tx type: 0x0 legacy, 0x2 EIP-1559, 0x54 Tempo Transaction, etc.

Use Cases

  • Inspecting a transaction after broadcast

  • Building transaction detail views in payment-focused wallets

  • Decoding TIP-20 transfer calldata for indexers

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?