For AI agents: a documentation index is available at /llms.txt. Markdown versions of pages are available by appending .md to any documentation URL.
Skip to main content

DEBUG methods

The DEBUG API methods allow you to inspect and debug the network. The DEBUG API is a more verbose alternative to the TRACE API, and its main purpose is compatibility with tools such as Remix. Where these APIs overlap, we recommend using the TRACE API for production use over the DEBUG API. Specifically, we recommend trace_block over debug_traceBlock, and trace_transaction over debug_traceTransaction.

note

The DEBUG API is not enabled by default for JSON-RPC. Enable it using the --rpc-http-api or --rpc-ws-api option.

The DEBUG methods are grouped into the following pages.

Trace​

Trace transactions, blocks, and calls.

  • debug_standardTraceBlockToFile
  • debug_standardTraceBadBlockToFile
  • debug_traceTransaction
  • debug_traceBlock
  • debug_traceBlockByHash
  • debug_traceBlockByNumber
  • debug_traceCall

Getters​

Retrieve block and transaction information.

  • debug_getBadBlocks
  • debug_getRawBlock
  • debug_getRawHeader
  • debug_getRawReceipts
  • debug_getRawTransaction

State and node​

Inspect account and world state, and manage node operations.

  • debug_accountAt
  • debug_accountRange
  • debug_batchSendRawTransaction
  • debug_metrics
  • debug_replayBlock
  • debug_resyncWorldState
  • debug_setHead
  • debug_storageRangeAt