eth_getBlockTransactionCountByHash

eth_getBlockTransactionCountByHash returns just the number of transactions in the Polygon PoS block identified by a given hash — a single hex integer, no block body. When all you need is how full a Bor block is, this is far lighter than pulling the entire block. Polygon's ~2-second blocks and low MATIC fees mean transaction counts fluctuate with demand, so this is a cheap pulse on activity. Send the hash to https://polygon.therpc.io/YOUR_API_KEY (chain ID 137, 0x89).

Use cases

• Quickly gauge how full a Polygon block is without downloading its full body.
• Validate that an indexed Bor block holds the expected transaction count after processing it.
• Measure Polygon throughput across a set of known block hashes to chart activity over time.

Parameters

Response

Example request

1curl https://polygon.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 Polygon playground.

Errors & troubleshooting

Common pitfalls

• An unknown hash returns null, not "0x0" — null-check before running parseInt on the result.
• When you have a Polygon block number rather than a hash and do not need hash-based certainty, use eth_getBlockTransactionCountByNumber instead.

Supported networks

• Mainnet — Chain ID: 137
• Amoy — Chain ID: 80002

See also

• eth_getBlockTransactionCountByNumber
• eth_getBlockByHash
• eth_getTransactionByBlockHashAndIndex

1curl https://polygon.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":[""]}'