eth_getBlockReceipts - Ronin
Example code for the eth_getBlockReceipts JSON-RPC method. Complete guide to using the eth_getBlockReceipts JSON-RPC method in the GetBlock.io Web3 documentation.
This method returns all transaction receipts for a block in a single call. It is used to read every transaction outcome and log in a block without one call per transaction.
Parameters
blockParameter
string
Yes
Block number in hex, block hash, or "latest", "earliest", "pending"
Request
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_getBlockReceipts",
"params": ["0x1e8480"],
"id": "getblock.io"
}'const axios = require('axios');
const response = await axios.post('https://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>/', {
jsonrpc: '2.0',
method: 'eth_getBlockReceipts',
params: ["0x1e8480"],
id: 'getblock.io'
}, {
headers: { 'Content-Type': 'application/json' }
});
console.log(response.data.result);import requests
response = requests.post(
'https://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>/',
headers={'Content-Type': 'application/json'},
json={
'jsonrpc': '2.0',
'method': 'eth_getBlockReceipts',
'params': ["0x1e8480"],
'id': 'getblock.io'
}
)
print(response.json())Response
{
"jsonrpc": "2.0",
"id": "getblock.io",
"result": [
{
"transactionHash": "0x4a7b0c3d6e9f2a5b8c1d4e7f0a3b6c9d2e5f8a1b4c7d0e3f6a9b2c5d8e1f4a7b",
"transactionIndex": "0x0",
"blockHash": "0x8e3f5b2a9c1d4e7f0a6b3c8d5e2f9a1b4c7d0e3f6a9b2c5d8e1f4a7b0c3d6e9f",
"blockNumber": "0x1e8480",
"from": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
"to": "0xe514d9deb7966c8be0ca922de8a064264ea6bcd4",
"gasUsed": "0x5208",
"cumulativeGasUsed": "0x5208",
"status": "0x1",
"logs": []
}
]
}Response Parameters
jsonrpc
string
JSON-RPC protocol version ("2.0")
id
string
Request identifier matching the request
result
array
Array of transaction receipt objects for the block
Receipt Object
transactionHash
string
Hash of the transaction
status
string
0x1 on success, 0x0 on failure
gasUsed
string
Gas used by the transaction
logs
array
Event logs emitted by the transaction
Use Cases
Block Indexing: Read all outcomes and logs for a block in one call
Event Pipelines: Ingest every log in a block efficiently
Reconciliation: Confirm the status of every transaction in a block
Analytics: Aggregate gas usage across a block's transactions
Error Handling
-32602
Invalid params
The block number or hash is malformed or out of range
-32603
Internal error
The node failed to read the block
Web3 Integration
Last updated
Was this helpful?