eth_getUncleByBlockHashAndIndex

Uncles never happen on BNB Smart Chain. Chain ID 56 runs PoSA consensus with fast deterministic finality, so the network never orphans a sibling block (the thing Ethereum calls an uncle or ommer). eth_getUncleByBlockHashAndIndex, reachable at https://bsc.therpc.io/YOUR_API_KEY, survives only as an Ethereum-compatibility shim. Per the original spec it would look up an ommer header by its position inside the block you name by hash. PoSA mints no such siblings, so the call resolves to null for whatever block hash and index pair you pass. Tools ported straight from Ethereum keep running against chain 56 without crashing; they simply read nothing back.

此链不支持该方法 — BSC runs PoSA consensus, which produces no uncle (ommer) blocks, so this method always returns null on chain 56.

Use cases

Compute uncle reward amounts during historical mining analysis. On PoSA BNB Smart Chain no such rewards exist, so this branch never fires.
Measure uncle rates as a proxy for network latency and validator competition; on chain 56 that metric reads as a structural zero.
Retrieve uncle header fields for cross-chain research tooling built around the Ethereum shape, accepting null as the BNB Smart Chain answer.

Parameters

#	名称	类型	必填	描述
1	`blockHash`	string (hex)	是	The hash of the block that references the uncle.
2	`uncleIndex`	string (hex)	是	Zero-based index of the uncle within the block's uncles array.

Response

类型	描述
object \| null	Block header object (no transactions array): number, hash, parentHash, sha3Uncles, miner, stateRoot, transactionsRoot, receiptsRoot, logsBloom, difficulty, gasLimit, gasUsed, timestamp, extraData, mixHash, nonce. Returns null if not found.

Example request

1curl https://bsc.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5    "jsonrpc": "2.0",
6    "method": "eth_getUncleByBlockHashAndIndex",
7    "params": [
8        "0x0000000000000000000000000000000000000000000000000000000000000000",
9        "0x0"
10      ],
11    "id": 1
12  }'

Try it live in the BNB Smart Chain playground.

Errors & troubleshooting

错误码	错误信息	原因
`-32602`	`Invalid params`	Block hash or uncle index is malformed.

Common pitfalls

Even on chains that do have uncles, an uncle header carries no transactions array — never parse one out of this result.
PoSA BNB Smart Chain produces no uncles at all, so queries against any block, recent or old, return null here.
The legacy Ethereum cap of two uncles per block does not save you on chain 56: index 0x0, 0x2, and everything else alike always resolve to null.

Supported networks

Mainnet — Chain ID: 56
Testnet — Chain ID: 97

1curl https://bsc.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5    "jsonrpc": "2.0",
6    "method": "eth_getUncleByBlockHashAndIndex",
7    "params": [
8        "0x0000000000000000000000000000000000000000000000000000000000000000",
9        "0x0"
10      ],
11    "id": 1
12  }'

错误码

错误信息

原因

-32602

Invalid params

Block hash or uncle index is malformed.

Common pitfalls

Even on chains that do have uncles, an uncle header carries no transactions array — never parse one out of this result.

PoSA BNB Smart Chain produces no uncles at all, so queries against any block, recent or old, return null here.

The legacy Ethereum cap of two uncles per block does not save you on chain 56: index 0x0, 0x2, and everything else alike always resolve to null.

eth_getUncleByBlockHashAndIndex

Use cases

Parameters

Response

Example request

Errors & troubleshooting

Common pitfalls

Supported networks

See also

准备好在生产环境中调用了吗？

eth_getUncleByBlockHashAndIndex

Use cases

Parameters

Response

Example request

Errors & troubleshooting

Common pitfalls

Supported networks

See also