Kaia

Kaia

eth_getBlockByNumber

eth_getBlockByNumber returns the full block matching a given height or tag. It's the most common way to fetch block-level data — used by explorers, indexers, monitoring stacks, and anything that needs to walk the chain backwards or forwards.

Parameters

The second argument is a real boolean, not the string "true" / "false" — your client should serialize it as true. The playground does this automatically.

Response shape (abbreviated)

1{
2  "jsonrpc": "2.0",
3  "id": 1,
4  "result": {
5    "number": "0x14a3b27",
6    "hash": "0x...",
7    "parentHash": "0x...",
8    "timestamp": "0x67b1234",
9    "miner": "0x...",
10    "gasUsed": "0xa8c2f0",
11    "gasLimit": "0x1c9c380",
12    "baseFeePerGas": "0x12a05f200",
13    "transactions": [
14      "0x...",
15      "0x..."
16    ]
17  }
18}

When includeTx: true, each entry in transactions[] is a full object: from, to, value, gas, maxFeePerGas, maxPriorityFeePerGas, input, nonce, r/s/v, accessList, and so on. The response gets large — for a popular block, expect 500–1500 KB.

Tips for indexers

1. Don't request full tx objects unless you need them. If you only care about hashes (you'll fetch receipts separately), pass includeTx: false — bandwidth drops 5-10×.
2. Use eth_getBlockReceipts instead of N + 1 calls. When you want the receipts of every tx in a block, one eth_getBlockReceipts call beats N eth_getTransactionReceipt calls.
3. Combine with finalized for safety. For systems of record, query against the finalized tag — those blocks can't be reorged.

See also

• eth_getBlockByHash — same data, looked up by hash.
• eth_getBlockReceipts — all receipts in a block in one call.
• eth_blockNumber — fetch the current chain height to choose which block to read.

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