Execution Trace
Read a transaction by call depth and understand how each step changes assets and state.
Execution Trace answers: how did this transaction execute step by step?
It organizes contract calls into a tree. A parent node is the context that made a call; child nodes are the next operations performed while that call is active.
Start with an example
Follow this transaction through the Trace
1. Start at the outermost level
Read Transaction, then expand CREATE. The transaction first creates an intermediate contract, and the remaining calls follow from that execution path.
2. Find where the asset enters
Expand UniswapV3Pool.flash(...) to find XPEPE.transfer(...). XPEPE moves from the pool into the intermediate contract, supplying the asset used by the later operations.
3. See what the intermediate contract does
The same branch contains TokenStaker.stake(...) and withdrawAll(), showing repeated staking and withdrawal actions. Continue to SwapRouter02 / Pool.swap(...) to connect these operations with receiving WETH.
4. Find the final outgoing transfer
Expand WETH.withdraw(...) to see WETH unwrapped into ETH. The final ETH transfers then send ETH to the transaction sender and fee recipient.
How to read a Trace
- Start at the outermost node and expand only the branches relevant to your question.
- Read the operation type first, such as
CALL,CREATE, orSTATICCALL, then the target and function name. - Use the toolbar to filter call types, choose an expansion depth, or search functions, addresses, and parameters.
- Select a node's detail control to inspect parameters, return values, gas, and errors.
- If a call is unclear, return to its parent node for context.
Notes
- Indentation shows call depth, not elapsed time. Siblings appear in execution order.
- An internal failure does not always fail the whole transaction; its parent may catch it.
- Function names and parameters depend on ABI, source, and signature decoding. Addresses and raw data remain useful when decoding is unavailable.