Breakpoint
Mark important trace nodes and move quickly between source, call stack, and state.
A breakpoint marks an Execution Trace node that you want to revisit. It does not rerun the transaction; it only helps you navigate and filter the existing trace.
Interactive example
The Debugger below uses local mock trace and source data. It does not request on-chain data. Hover next to an Execution Trace number and click the dot to add or remove a breakpoint.
How to use it
- Open a transaction in Debugger and find the call or instruction you need to inspect in Execution Trace.
- Click the dot beside its trace number. A red dot means the breakpoint is set.
- The Breakpoints panel appears after the first breakpoint is added.
- Select an item in the panel to jump to its trace, or use Previous / Next to move between breakpoints.
To focus on those nodes, enable Breakpoints Only at the top of the trace. The list keeps the breakpoints and their hierarchy. Disable it to return to the full trace.
Breakpoint groups
In Variable History for a variable or storage slot, click Set Breakpoints. All related writes are added to one group. Expand the group to compare the call stack, parameters, and state for each write.
Notes
- Click × beside a breakpoint or breakpoint group to remove it.
- Breakpoints are saved in the current browser by network and transaction hash, so they remain available when you reopen the same transaction.
- Breakpoints are attached to trace nodes, not source lines. They also work in Bytecode Mode when source is unavailable.
- For
DELEGATECALL, verify both the executing-code address and the state address.