Avalanche

Avalanche

debug_traceTransaction

The debug_traceTransaction method recreates the exact execution state of a historical transaction, providing detailed opcode-level trace information. It reproduces the original state at the specific block where the transaction was executed, allowing for complete analysis of transaction execution flow, stack operations, memory changes, storage modifications, and gas consumption.

Unlike other transaction retrieval methods that only provide basic transaction data, debug_traceTransaction offers introspection into the internal execution of the EVM during transaction processing.

Use Cases

• Failed Transaction Analysis: Determine exactly why a transaction failed by examining the precise instruction that caused the revert and the EVM state at that point
• Smart Contract Debugging: Investigate unexpected behavior in contract execution by examining the complete execution pathway and state changes
• Gas Usage Optimization: Identify expensive operations and inefficient code patterns by analyzing gas consumption per opcode
• Security Auditing: Detect potential vulnerabilities by analyzing the exact execution flow and state transitions during transaction processing
• Transaction Verification: Confirm that a contract behaved as expected for a specific transaction by reviewing all operations performed
• Contract State Inspection: View the exact changes made to contract storage during transaction execution
• Forensic Investigation: Reconstruct transaction execution for investigating security incidents or analyzing historical events
• Call Graph Analysis: Visualize the execution flow between contracts including internal function calls and message values
• Finding State Inconsistencies: Identify unexpected state changes during complex contract interactions
• Recreating Execution Context: Reproduce the exact blockchain environment that existed when the transaction executed

Method Details

This method traces the transaction identified by its hash, providing opcode-level execution details.

Response Example (Default Tracer)

1{
2	"jsonrpc": "2.0",
3	"id": 1,
4	"result": {
5		"gas": 21000,
6		"failed": false,
7		"returnValue": "",
8		"structLogs": [
9			{
10				"pc": 0,
11				"op": "PUSH1",
12				"gas": 4677951,
13				"gasCost": 3,
14				"depth": 1,
15				"stack": [],
16				"memory": [],
17				"storage": {}
18			},
19			{
20				"pc": 2,
21				"op": "MSTORE",
22				"gas": 4677948,
23				"gasCost": 12,
24				"depth": 1,
25				"stack": ["0x60", "0x40"],
26				"memory": [
27					"0000000000000000000000000000000000000000000000000000000000000000",
28					"0000000000000000000000000000000000000000000000000000000000000000"
29				],
30				"storage": {}
31			}
32			// Many more opcode logs...
33		]
34	}
35}

Response Example (callTracer)

1{
2  "jsonrpc": "2.0",
3  "id": 1,
4  "result": {
5    "from": "0x8894e0a0c962cb723c1976a4421c95949be2d4e3",
6    "gas": "0x2d48c",
7    "gasUsed": "0x594c",
8    "to": "0x55d398326f99059ff775485246999027b3197955",
9    "input": "0xa9059cbb000000000000000000000000b5cfcb4b073ebcda22f57097dbd0e0be5731ca5c00000000000000000000000000000000000000000000000011c37937e08000",
10    "output": "0x0000000000000000000000000000000000000000000000000000000000000001",
11    "calls": [
12      {
13        "type": "CALL",
14        "from": "0x55d398326f99059ff775485246999027b3197955",
15        "to": "0xb5cfcb4b073ebcda22f57097dbd0e0be5731ca5c",
16        "gas": "0x1e25b",
17        "gasUsed": "0x30b",
18        "input": "0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
19        "output": "0x"
20      }
21    ],
22    "value": "0x0"
23  }
24}

Common Issues Identified Through Tracing

• Out of gas errors
• Stack underflows or overflows
• Invalid opcode execution
• Failed assertions or require conditions
• Unexpected reverts
• Memory allocation issues
• Unexpected contract state
• Transfer failures
• Access control issues
• Logic errors

Available Tracers

1. Default Tracer: Returns structured logs for each opcode
2. callTracer: Shows call graph between contracts
3. prestateTracer: Shows state before transaction execution
4. 4byteTracer: Collects function selectors
5. noopTracer: Discards all information
6. Custom JavaScript Tracers: Create your own tracer logic

Trace Options

You can tune performance and output by configuring these options:

• Disable stack, memory, or storage capturing for faster execution
• Use custom timeout for complex transactions
• Apply custom tracer configurations for specific analysis needs

Performance Considerations

• Tracing complex transactions can be resource-intensive and slow
• Large contracts with many operations may produce very large response payloads
• Using options to disable certain captures (memory, storage, stack) can improve performance
• Consider using a specific custom tracer for targeted analysis rather than capturing everything
• Tracing transactions that create contracts with large initialization code can be particularly intensive
• Transactions with many internal calls or high call depth require more resources to trace

Important Notes

• This method requires debug APIs to be enabled on the node (usually with --http.api=debug flag)
• debug_traceTransaction provides more detailed information than trace_transaction
• For accurate results, you need access to the historical state at the block where the transaction occurred
• Archive nodes are required for tracing older transactions
• Some clients may not support all tracer types
• Custom JavaScript tracers are only available on Geth and some Geth-compatible clients
• This method will replay the transaction exactly as it occurred, including any side effects
• The trace does not include events/logs (these must be queried separately)
• Some operations like BLOCKHASH have their results from the original execution cached and reused
• Using this method on transactions in very old blocks may result in state inconsistencies on some nodes

See also

• debug_traceCall - Execute a call without generating a transaction and return the trace data
• debug_traceCallMany - Execute multiple calls without generating transactions and return trace data
• trace_transaction - Return trace data for a specific transaction
• eth_getTransactionByHash - Retrieve basic transaction information by hash
• eth_getTransactionReceipt - Get transaction receipt information by hash

1curl https://avalanche.therpc.io \
2  -X POST \
3  -H 'Content-Type: application/json' \
4  -d '{"jsonrpc":"2.0","id":1,"method":"debug_traceTransaction","params":["",{"tracer":"callTracer"}]}'