trace_block

A BSC block closes about every three seconds, and on a busy one that can mean a few hundred transactions packed with BEP-20 transfers and DeFi calls. trace_block hands you the call-tree trace for all of them at once. Pass a height in hex or a tag like latest; you get back a single flat array where each entry names a call, create, or self-destruct action and carries the transactionPosition of the transaction that produced it. Point the request at chain ID 56 on https://bsc.therpc.io/YOUR_API_KEY. This is the block-wide view, tuned for fund-flow and MEV work rather than opcode-by-opcode debugging. It is heavy, and it only runs against a trace-enabled archive node.

Use cases

• Pull every internal transaction in a block in one shot to feed an indexer or analytics pipeline.
• Spot sandwiches and back-runs by reading MEV activity across all the transactions in a single block.
• Watch BNB and token value move into and out of a contract over the span of one whole block.

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

Try it live in the BNB Smart Chain playground.

Errors & troubleshooting

Common pitfalls

• One call returns every trace for every transaction, so a high-throughput BSC block can produce a very large payload.
• The trace namespace runs only on a trace-enabled archive node, and plenty of public endpoints either hide it or throttle it on lower tiers.
• Skip the pending tag for production data. Those traces can still change before the block finalizes.

Supported networks

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

See also

• trace_transaction
• trace_filter
• trace_replayBlockTransactions
• debug_traceBlockByNumber

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