Polygon
Polygon
Polygon
免费套餐涵盖个人项目。按量付费,无需绑卡即可扩展。
debug_traceBlockByHash re-executes a whole Polygon PoS block and hands back a trace for each transaction it contains, selected by the block's hash rather than its number. Polygon's Bor client is Geth-based, so the same tracers you use on Ethereum — callTracer, prestateTracer, or the default opcode struct-log — apply here against MATIC-fee blocks. Send the request to https://polygon.therpc.io/YOUR_API_KEY (chain ID 137, 0x89). It returns opcode-level execution traces for every transaction in the block identified by its hash, in block order.
callTracer.| # | 名称 | 类型 | 必填 | 描述 |
|---|---|---|---|---|
| 1 | blockHash | string | 是 | Hash of the block to trace. |
| 2 | options | object | 否 | Same tracer configuration object as debug_traceTransaction. |
| 类型 | 描述 |
|---|---|
| array | Array of per-transaction trace results in block order. Each element has the same shape as debug_traceTransaction output for the active tracer. |
Try it live in the Polygon playground.
| 错误码 | 错误信息 | 原因 |
|---|---|---|
-32601 | Method not found | debug namespace not enabled on the node. |
-32602 | Invalid params | Block hash is missing or not a valid 32-byte hex value. |
-32000 | block not found | Block hash not found or archive state unavailable. |
debug_traceBlockByNumber: the node replays every transaction in the block, so a dense Polygon block is far heavier than a single-transaction trace.参数
0x-prefixed 32-byte block hash
Same tracer configuration object as debug_traceTransaction.