debug_traceTransaction - Linea RPC Method

Traces a transaction execution on Linea by transaction hash.

When to Use This MethodCopy Anchor Link

• Analyze transaction execution step-by-step - Trace every opcode and internal call in a completed transaction for enterprise DeFi (Aave, Renzo), institutional cross-border payments via SWIFT pilots, and zkEVM-native applications
• Debug failed transactions - Pinpoint the exact opcode and call depth where a transaction reverted on Linea
• 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 PracticesCopy Anchor Link

• 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

{
  "jsonrpc": "2.0",
  "method": "debug_traceTransaction",
  "params": ["0xc9e9cb9405a8e526ee8eb21e2aae56fe6df29590f8e4d44148f15c8f6a263128", {"tracer": "callTracer"}],
  "id": 1
}

Tracer OptionsCopy Anchor Link

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

Code ExamplesCopy Anchor Link

Related MethodsCopy Anchor Link

• debug_traceCall - Trace without executing
• debug_traceBlockByNumber - Trace entire block