trace_block

trace_block returns the OpenEthereum-style call tree for every transaction in a single Polygon PoS block, flattened into one array. Unlike the opcode-level debug_* tracers, it focuses on the call/create/self-destruct actions and the MATIC value moving between contracts — the level most indexers and explorers want. Send the request to https://polygon.therpc.io/YOUR_API_KEY (chain ID 137, 0x89), naming the block by number or a tag like latest. It returns call-tree traces for every transaction in that block.

Use cases

• Extract all internal MATIC transfers in a Polygon block for an indexer or analytics pipeline, including transfers that emit no event.
• Analyze MEV activity across every transaction in a specific block — useful given Polygon's dense DEX and arbitrage traffic.
• Track value flows into and out of a contract (a QuickSwap pair, an Aave market) for an entire block at once.

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

Try it live in the Polygon playground.

Errors & troubleshooting

Common pitfalls

• It returns every trace for every transaction, so a high-throughput Polygon block can produce a very large response — page through blocks rather than batching many at once.
• It needs a trace-enabled Bor archive node; ordinary full nodes do not retain the trace data.
• Avoid pending for production data — a Polygon block is only ~2 seconds away and the pending set can change, and finality only settles once it is checkpointed to L1 via Heimdall.

Supported networks

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

See also

• trace_transaction
• trace_filter
• trace_replayBlockTransactions
• debug_traceBlockByNumber

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