debug_traceCall

debug_traceCall runs a call against a chosen Polygon PoS block state and traces it in full, all without broadcasting a transaction or spending any MATIC on gas. Because Polygon's Bor client is Geth-based, you get the same tracer choices as on Ethereum — callTracer, prestateTracer, or the default struct-log — plus optional state and block overrides for what-if simulations. Send the request to https://polygon.therpc.io/YOUR_API_KEY (chain ID 137, 0x89). It executes the call against the given block state and returns a full opcode-level trace without submitting a transaction.

Use cases

• Debug a Polygon contract interaction before broadcasting by tracing the exact execution path and the revert reason — handy for QuickSwap or Aave calls.
• Simulate how a call would behave at a historical Polygon block height (past blocks need a Bor archive node).
• Profile the gas a prospective transaction would burn without spending any MATIC.
• Test proposed contract logic against live Polygon state using stateOverrides to swap in modified bytecode.

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": "debug_traceCall",
7    "params": [
8        {
9          "to": "0x0000000000000000000000000000000000000000",
10          "data": "0x"
11        },
12        "latest",
13        {},
14        {},
15        {}
16      ],
17    "id": 1
18  }'

Try it live in the Polygon playground.

Errors & troubleshooting

Common pitfalls

• The call is simulated against one block's state, so results can drift from real execution when the contract reads block-specific context like the Bor block producer (coinbase) or timestamp — override those explicitly if they matter.
• Tracing against a historical Polygon block state requires a Bor archive node; recent state is enough for latest.
• For complex Polygon DeFi contracts the response can be huge — reach for a compact tracer like callTracer, or disable stack, memory, and storage in the options to keep it manageable.

Supported networks

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

See also

• debug_traceTransaction
• trace_call
• debug_storageRangeAt
• 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":"debug_traceCall","params":[{"to":"0x0000000000000000000000000000000000000000","data":"0x"},"latest",{}]}'