trace_filter

trace_filter scans a range of Polygon PoS blocks and returns only the traces that match your criteria — a sender or recipient address, a block range, plus offset/count pagination. It is the query tool of the trace namespace: where trace_block and trace_transaction give you everything for one block or one transaction, this lets you follow a single MATIC address or contract across many blocks at once. Send the request to https://polygon.therpc.io/YOUR_API_KEY (chain ID 137, 0x89). It searches for traces matching criteria across a range of blocks.

Use cases

• Find every internal MATIC transfer sent to a contract across a range of Polygon blocks, including ones that emit no event.
• Detect MEV bot activity by filtering traces from known Polygon bot addresses over a block window.
• Build an indexer for all calls to a specific Polygon DeFi protocol such as QuickSwap or Aave.
• Run forensic analysis of every interaction with a contract before and after an exploit, by address and block range.

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

Try it live in the Polygon playground.

Errors & troubleshooting

Common pitfalls

• Wide block ranges are very slow and often rejected: Polygon mints a block every ~2 seconds, so even a single day spans tens of thousands of blocks — always narrow fromBlock/toBlock and page with offset and count.
• It needs a trace-enabled Bor archive node; most public Polygon endpoints do not expose this method at all.
• Unlike eth_getLogs, traces are not indexed by topic — you can filter only by address and block number, so there is no event-signature shortcut.

Supported networks

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

See also

• trace_transaction
• trace_block
• trace_call
• trace_replayTransaction

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