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

eth_getTransactionReceipt - zkSync

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

Returns the receipt for a transaction, including execution status, gas used, emitted logs, and L1 batch metadata. Available after the transaction has been included in an L2 block.

Parameters

Parameter
Type
Required
Description

transactionHash

string

Yes

32-byte hash of the transaction

Request Example

curl --location --request POST 'https://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "eth_getTransactionReceipt",
    "params": [
        "0x22de7debaa98758afdaee89f447ff43bab5da3de6acca7528b281cc2f1be2ee9"
    ],
    "id": "getblock.io"
}'
import axios from 'axios';

const data = JSON.stringify({
    "jsonrpc": "2.0",
    "method": "eth_getTransactionReceipt",
    "params": [
        "0x22de7debaa98758afdaee89f447ff43bab5da3de6acca7528b281cc2f1be2ee9"
    ],
    "id": "getblock.io"
});

const config = {
    method: 'post',
    url: 'https://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>/',
    headers: {
        'Content-Type': 'application/json'
    },
    data: data
};

axios(config)
    .then(response => console.log(JSON.stringify(response.data, null, 2)))
    .catch(error => console.log(error));

Response Example

{
    "jsonrpc": "2.0",
    "id": "getblock.io",
    "result": {
        "blockHash": "0x4f3a1d6e8c2b9a7e5d3f1c8a4b6e9d2f5a8c3e7b1d4f9a6c2e5b8d3f7a1c4e9b",
        "blockNumber": "0x2249b7",
        "contractAddress": null,
        "cumulativeGasUsed": "0x12345",
        "effectiveGasPrice": "0xee6b280",
        "from": "0x36615cf349d7f6344891b1e7ca7c72883f5dc049",
        "gasUsed": "0x12345",
        "logs": [],
        "logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
        "status": "0x1",
        "to": "0xd85498dbeaeb1df24be52eed4f52eac2fbd56245",
        "transactionHash": "0x22de7debaa98758afdaee89f447ff43bab5da3de6acca7528b281cc2f1be2ee9",
        "transactionIndex": "0x0",
        "type": "0x2",
        "l1BatchNumber": "0x72582",
        "l1BatchTxIndex": "0x5"
    }
}

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 (hex, in wei)

result.logs

array

Logs emitted by the transaction

result.contractAddress

string

null if this was a contract creation; deployed contract address

result.l1BatchNumber

string

L1 batch number (zkSync extension)

Use Cases

  • Confirming transaction success or failure after broadcast

  • Reading emitted events from contract interactions

  • Computing actual gas cost for analytics

  • Determining the L1 batch that contained the transaction

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?