eth_getUncleCountByBlockNumber

Chain ID 56 finalizes one canonical block per PoSA slot in roughly three seconds, paying gas in BNB, and never accumulates competing sibling blocks along the way. eth_getUncleCountByBlockNumber, issued against https://bsc.therpc.io/YOUR_API_KEY, is documented to count the ommers a block references when you address that block by height or by a tag like latest. Whether you name the block by number or by hash makes no difference to the result. PoSA forks no uncles, so this variant stays an Ethereum-compatibility shim that hands back 0x0 at every height you ask about.

Use cases

• Iterate a contiguous span of block heights to tally uncle presence and derive an uncle rate; across BNB Smart Chain that tally stays pinned at zero, evidencing PoSA's fork-free design.
• Run a fast gate before requesting uncle details with eth_getUncleByBlockNumberAndIndex; a 0x0 count tells you up front there is nothing further to fetch at that height.

Parameters

Response

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_getUncleCountByBlockNumber",
7    "params": ["latest"],
8    "id": 1
9  }'

Try it live in the BNB Smart Chain playground.

Errors & troubleshooting

Common pitfalls

• Under PoSA, BNB Smart Chain returns 0x0 for every height regardless of which block you name, so never branch on the expectation of a positive count.
• The value arrives as a hex string, not an integer; decode 0x0 to a number before any numeric comparison or you risk comparing strings by accident.

Supported networks

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

See also

• eth_getUncleByBlockNumberAndIndex
• eth_getUncleCountByBlockHash
• eth_getBlockByNumber

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