eth_getBlockReceipts

eth_getBlockReceipts returns every transaction receipt for a given Arbitrum One block in a single call. On this high-throughput Optimistic Rollup — where gas is paid in ETH and blocks can be busy with GMX, Uniswap, and Aave activity — it is far more efficient than fetching receipts one transaction at a time. Point it at https://arbitrum.therpc.io/YOUR_API_KEY (chain ID 42161) with a block number or tag to pull the whole batch at once.

Use cases

• Ingest every event in an Arbitrum One block for indexing with a single RPC call instead of one per transaction.
• Calculate total gas used and ETH fees across all transactions in a block.
• Scan all ERC-20 Transfer logs in a block to update token balances (USDC, ARB, and other Arbitrum tokens).
• Identify failed transactions in a block — status "0x0" — for error analysis and alerting.

Parameters

Response

Example request

1curl https://arbitrum.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5    "jsonrpc": "2.0",
6    "method": "eth_getBlockReceipts",
7    "params": ["latest"],
8    "id": 1
9  }'

Try it live in the Arbitrum One playground.

Errors & troubleshooting

Common pitfalls

• Much more efficient than N separate eth_getTransactionReceipt calls — always prefer this for block-level receipt ingestion on Arbitrum One.
• A response for a busy block with verbose logs can be large; stream or chunk your processing rather than buffering the whole array in memory.
• Not every node or provider exposes eth_getBlockReceipts; confirm availability on your endpoint before relying on it in production.

Supported networks

• Mainnet — Chain ID: 42161
• Sepolia — Chain ID: 421614

See also

• eth_getTransactionReceipt
• eth_getBlockByNumber
• eth_getLogs
• eth_getTransactionByHash

1curl https://arbitrum.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H 'Content-Type: application/json' \
4  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getBlockReceipts","params":[""]}'