Docs

debug_traceTransaction - Arbitrum RPC Method

Trace a transaction execution on Arbitrum. Requires archive node for debugging high-volume DeFi (GMX, Uniswap, Aave), gaming, and cross-chain applications.

Traces a transaction execution on Arbitrum by transaction hash.

Archive Node Required

This method requires an archive node. It is not available on full nodes.

When to Use This Method

  • Analyze transaction execution step-by-step - Trace every opcode and internal call in a completed transaction for high-volume DeFi (GMX, Uniswap, Aave), gaming, and cross-chain applications
  • Debug failed transactions - Pinpoint the exact opcode and call depth where a transaction reverted on Arbitrum
  • Examine internal call traces - Follow the full call tree including delegate calls and contract creations
  • Gas usage profiling - Measure gas consumption per opcode to identify optimization opportunities

Best Practices

  • Requires archive node access; not available on standard full nodes
  • Traces can be very large for complex transactions with many internal calls
  • Use tracer options like onlyTopCall or callTracer to limit output size
  • Store traces off-chain for analysis rather than querying repeatedly

Tracer Options

  • {} - Default opcode tracer (verbose)
  • { tracer: "callTracer" } - Call tree tracer
  • { tracer: "prestateTracer" } - Pre-state tracer

Code Examples

debug_traceCall

Trace a call without creating a transaction on Arbitrum. Simulate transactions, debug contract interactions, and analyze gas usage with full execution traces.

eth_chainId

Get the chain ID for Arbitrum. Essential for transaction signing and network verification.

On this page

When to Use This MethodBest PracticesTracer OptionsCode ExamplesRelated Methods