Taiko

Taiko

trace_transaction

The trace_transaction method retrieves detailed trace information for a transaction identified by its hash. This method provides insight into every step of the transaction's execution, including internal calls between contracts, allowing for in-depth analysis and debugging.

Use Cases

• Debugging specific transactions to identify errors
• Analyzing gas consumption for individual operations
• Tracing internal calls within a transaction
• Understanding complex contract interactions
• Investigating transaction failures
• Security auditing and vulnerability analysis
• Verifying expected contract behavior
• Tracking funds flow across multiple contracts
• Analyzing execution patterns of similar transactions
• Debugging failed or reverted transactions

Method Details

This method returns an array of traces for all operations executed during the transaction.

Response Example

1{
2	"jsonrpc": "2.0",
3	"id": 1,
4	"result": [
5		{
6			"action": {
7				"callType": "call",
8				"from": "0x83806d539d4ea1c140489a06660319c9a303f874",
9				"gas": "0x1a1f8",
10				"input": "0x",
11				"to": "0x1c39ba39e4735cb65978d4db400ddd70a72dc750",
12				"value": "0x7a16c911b4d00000"
13			},
14			"blockHash": "0x7eb25504e4c202cf3d62fd585d3e238f592c780cca82dacb2ed3cb5b38883add",
15			"blockNumber": 3068185,
16			"result": {
17				"gasUsed": "0x2982",
18				"output": "0x"
19			},
20			"subtraces": 2,
21			"traceAddress": [],
22			"transactionHash": "0x17104ac9d3312d8c136b7f44d4b8b47852618065ebfa534bd2d3b5ef218ca1f3",
23			"transactionPosition": 2,
24			"type": "call"
25		},
26		{
27			"action": {
28				"callType": "call",
29				"from": "0x1c39ba39e4735cb65978d4db400ddd70a72dc750",
30				"gas": "0x13e99",
31				"input": "0x16c72721",
32				"to": "0x2bd2326c993dfaef84f696526064ff22eba5b362",
33				"value": "0x0"
34			},
35			"blockHash": "0x7eb25504e4c202cf3d62fd585d3e238f592c780cca82dacb2ed3cb5b38883add",
36			"blockNumber": 3068185,
37			"result": {
38				"gasUsed": "0x183",
39				"output": "0x0000000000000000000000000000000000000000000000000000000000000001"
40			},
41			"subtraces": 0,
42			"traceAddress": [0],
43			"transactionHash": "0x17104ac9d3312d8c136b7f44d4b8b47852618065ebfa534bd2d3b5ef218ca1f3",
44			"transactionPosition": 2,
45			"type": "call"
46		},
47		{
48			"action": {
49				"callType": "call",
50				"from": "0x1c39ba39e4735cb65978d4db400ddd70a72dc750",
51				"gas": "0x8fc",
52				"input": "0x",
53				"to": "0x70faa28a6b8d6829a4b1e649d26ec9a2a39ba413",
54				"value": "0x7a16c911b4d00000"
55			},
56			"blockHash": "0x7eb25504e4c202cf3d62fd585d3e238f592c780cca82dacb2ed3cb5b38883add",
57			"blockNumber": 3068185,
58			"result": {
59				"gasUsed": "0x0",
60				"output": "0x"
61			},
62			"subtraces": 0,
63			"traceAddress": [1],
64			"transactionHash": "0x17104ac9d3312d8c136b7f44d4b8b47852618065ebfa534bd2d3b5ef218ca1f3",
65			"transactionPosition": 2,
66			"type": "call"
67		}
68	]
69}

Understanding the Trace Tree

The trace tree represents the execution flow of the transaction:

1. Root level trace: The main transaction (empty traceAddress)
2. Subtrace level 1: Internal calls directly from the main transaction (traceAddress of [0], [1], etc.)
3. Deeper levels: Subsequent internal calls (traceAddress of [0, 0], [0, 1], etc.)

Call Types

The callType field may have different values:

• call: A regular message call
• delegatecall: A call where the code is executed in the context of the caller
• staticcall: A read-only call (no state modifications allowed)
• callcode: Similar to delegatecall but with the value passed (legacy)

Trace Types

The type field indicates the operation type:

• call: A message call
• create: A contract creation
• suicide: A contract self-destruct (SELFDESTRUCT opcode)

Important Notes

• This method requires trace APIs to be enabled on the Ethereum node
• The response can be very large for complex transactions with many internal calls
• The method is computationally intensive and may take time to complete for complex transactions
• Not all Ethereum clients support this method
• Historical transactions can only be traced if the node maintains archive data
• Some clients may have limitations on how far back transactions can be traced
• For more detailed VM-level execution traces, consider using trace_replayTransaction
• Unlike event logs, traces capture all contract interactions including those that don't emit events
• Failed transactions will still produce traces up to the point of failure
• SELFDESTRUCT operations appear with type "suicide" for historical reasons

See also

• trace_filter - Search for traces based on criteria
• trace_block - Retrieve traces for all transactions in a block
• trace_replayTransaction - Get more detailed traces with state changes
• debug_traceTransaction - Alternative detailed transaction tracing

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