trace_replayBlockTransactions

Where trace_block gives you only the call tree, trace_replayBlockTransactions re-executes every transaction in a BSC block from scratch and lets you keep up to three artifacts per transaction: the call-tree trace, the opcode-level vmTrace, and the stateDiff. You choose which through traceTypes. Point it at chain ID 56 via https://bsc.therpc.io/YOUR_API_KEY. The state diff is what earns the cost. For each transaction it records the precise balance, nonce, code, and storage mutations the execution caused. Replaying a whole block this way is the most demanding call in the trace namespace, and it only works against a trace-enabled archive node holding that block's state.

Use cases

Generate a full state-diff audit for every transaction in a block and feed it into a chain analytics pipeline.
Rebuild all BNB and token balance changes inside a block for accounting or reconciliation.
Replay a known MEV block end to end to see exactly how the bundle played out.

Parameters

#	Name	Type	Required	Description
1	`blockParameter`	string	Yes	Block whose transactions to replay.
2	`traceTypes`	array	Yes	One or more of `"trace"`, `"vmTrace"`, `"stateDiff"`. At least one value is required.

Response

Type	Description
array	Array of per-transaction replay results in block order. Each element has the same shape as trace_replayTransaction output, plus `transactionHash`.

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_replayBlockTransactions",
7    "params": [
8        "latest",
9        [
10          "trace"
11        ]
12      ],
13    "id": 1
14  }'

Try it live in the BNB Smart Chain playground.

Errors & troubleshooting

Code	Message	Cause
`-32601`	`Method not found`	trace namespace not enabled or not supported by this client.
`-32602`	`Invalid params`	blockParameter is malformed or traceTypes is empty or contains unknown values.
`-32000`	`block not found`	Block does not exist or archive trace data is unavailable for that block.

Common pitfalls

It is the costliest call in the trace namespace. Replaying every transaction and computing each requested trace type can time out on a busy block.
A trace-enabled archive node is required, and lower service tiers often rate-limit or refuse the call outright.
All three traceTypes on a dense block can return hundreds of megabytes, so ask for the narrowest set of artifacts that answers your question.

Supported networks

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