debug_traceTransaction - IoTeX RPC Method

Traces a transaction execution on IoTeX by transaction hash.

When to Use This Method

• Analyze transaction execution step-by-step - Trace every opcode and internal call in a completed transaction for decentralized physical infrastructure (DePIN), IoT device identity (ioID), and AI-verified real-world data
• Debug failed transactions - Pinpoint the exact opcode and call depth where a transaction reverted on IoTeX
• 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

Related Methods

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