Debug and trace APIs allow Web3 developers to monitor, trace, and debug the activities that occur within blockchain networks.
debug_*
namespace is exposed.debug_*
and trace_*
namespaces are exposed.debug_*
namespace is exposed.debug_*
and trace_*
namespaces are exposed.debug_*
namespace is exposed.debug_*
and trace_*
namespaces are exposed.debug_trace*
.
For a full list of the Geth debug API methods, see the Debug namespace section of the Geth documentation.
You can deploy a dedicated Avalanche node starting from a paid plan.
debug_*
and arbtrace_*
methods.
Blocks older than 22,207,815th were added to the chain before Nitro migration and cannot be queried with Geth methods. Starting from block 22,207,815, Arbitrum migrated to Nitro which made Geth debug_*
methods available for newer blocks.
Use the following methods for calling on blocks prior to 22,207,815:
debug_*
namespace methods, see Geth documentation.
debug_*
API methods. A debug and trace node for zkSync Era is available starting from a paid plan.
debug_*
and trace_*
API methods. A dedicated debug and trace node for Gnosis Chain is available starting from a paid plan.
For the full list of the available debug and trace API methods, see Nethermind documentation.
debug_*
API methods. A dedicated debug and trace node for Fantom is available starting from a paid plan.
For the full list of the available debug and trace API methods, see Debug namespace.
debug_*
API methods. A dedicated debug and trace node for Harmony is available starting from a paid plan.
For the full list of the available debug and trace API methods, see Debug namespace.
debug_traceBlockByNumber
in block 14,976,695:
0xE486B7
— the number of the block to get the traces of included transactions. For Geth, you need to provide the block number in hex.trace_block
in block 14,976,695:
14976695
— the number of the block to get the traces of included transactions