eth_getTransactionByBlockNumberAndIndex

When you are stepping through BNB Smart Chain by height rather than by hash, eth_getTransactionByBlockNumberAndIndex is the tool to reach a single transaction. Pass a hex block number or a tag such as latest or pending, add a zero-based hex index, and the node returns that one transaction object. You get null if the height or position has no entry. BNB Smart Chain charges gas in BNB and seals blocks about every three seconds, so iterating height-by-height keeps pace with a quick chain. Send each request to https://bsc.therpc.io/YOUR_API_KEY on chain ID 56.

Use cases

• Sweep across consecutive heights pulling the leading transaction of each block to study ordering and MEV behaviour on BSC.
• Inspect a queued transaction at a known mempool position by combining the pending tag with its index.
• Scan blocks in sequence when you already hold the height numbers and have no need to resolve a block hash first.

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_getTransactionByBlockNumberAndIndex",
7    "params": [
8        "latest",
9        "0x0"
10      ],
11    "id": 1
12  }'

Try it live in the BNB Smart Chain playground.

Errors & troubleshooting

Common pitfalls

• Encode the index as hex — write "0x0" for the leading transaction, never a plain numeric 0.
• How the pending tag orders and exposes queued transactions is not uniform across node clients, so do not depend on stable positions there.

Supported networks

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

See also

• eth_getTransactionByBlockHashAndIndex
• eth_getTransactionByHash
• 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_getTransactionByBlockNumberAndIndex","params":["",""]}'