BNB Smart Chain

BNB Smart Chain

eth_getBlockTransactionCountByHash

eth_getBlockTransactionCountByHash answers a single question about a BNB Smart Chain block: how many transactions it contains, looked up by the block's 32-byte hash. It skips the payload entirely and just returns the tally as hex. BNB Smart Chain is the BNB-gas, PoSA-validator EVM, so this count reflects exactly what one canonical, uncle-free block sealed. Send the hash to https://bsc.therpc.io/YOUR_API_KEY at chain ID 56 and you get back that number alone — a cheap way to gauge how busy the block was.

Use cases

• Gauge how full a BSC block was without paying to download its entire body.
• Cross-check that an indexer captured the expected transaction count for a block it already processed.
• Sample throughput across a set of known block hashes to chart BSC activity over time.

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

Try it live in the BNB Smart Chain playground.

Errors & troubleshooting

Common pitfalls

• An unrecognized hash comes back as null rather than an error, so null-check before you feed the result into parseInt.
• If you only hold a height and do not need hash-level certainty, eth_getBlockTransactionCountByNumber is the simpler counterpart to reach for.

Supported networks

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

See also

• eth_getBlockTransactionCountByNumber
• eth_getBlockByHash
• eth_getTransactionByBlockHashAndIndex

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_getBlockTransactionCountByHash","params":[""]}'