Call Graph
Quickly inspect the call relationships and main execution paths between addresses in a transaction.
Call Graph shows call relationships in a transaction: nodes are addresses or contracts, and edges are calls.
Start from the transaction sender and follow the arrows through routers, pools, or application contracts. Use the graph to identify the main path before opening Trace for details.
Example
Reading the graph
- Start at the sender and inspect the contracts it calls directly. Multiple outgoing edges mean that the address makes multiple calls.
- Find the target address or highly connected nodes to see whether execution passes through a Router, Pool, Vault, or application contract.
- Once you have a call relationship to inspect, open Execution Trace and search by address or call to view its function, parameters, and order.
Using Merge
With Merge enabled, repeated calls between the same caller and target are combined to keep the graph readable. Disable it when you need to distinguish separate calls between the same pair of contracts.
Controls
| Control | Purpose |
|---|---|
| Merge | Combines repeated call relationships. |
| Static Call | Shows or hides read-only calls. |
| Delegated Call | Shows or hides delegated calls such as DELEGATECALL; enable it when analyzing a proxy. |
| Zoom / fit | Inspect a local area or fit the entire graph back into view. |
| Minimap | Shows or hides an overview of the graph. |
Notes
- Call Graph does not show asset movement. Use Token Flow for asset sources, paths, and destinations.
- A merged edge can represent more than one call.
- Use Execution Trace for function parameters, return values, and
REVERTreasons.