Token Flow
Follow real transfer paths through addresses, contracts, and asset conversions.
Token Flow answers: which addresses did an asset pass through, and how did it reach its destination?
It preserves intermediate transfers, making it useful for swaps, routers, pools, wrapping, unwrapping, and complex contract interactions.
Start with an example
Read this transaction step by step
1. Find the source of XPEPE
Use the filter to focus on XPEPE. The edge from UniswapV3Pool to Exploit Contract shows XPEPE first moving from the pool into the intermediate contract.
Each edge tells you where the asset came from, which address it passed through, and how much moved.
2. Follow the TokenStaker round trip
Continue along the XPEPE edges between Exploit Contract and TokenStaker, then observe XPEPE returning to the pool.
Select an edge to open Tracking Flow. Use the previous and next buttons to follow related transfers in order. When an asset moves back and forth across several contracts, read the sequence rather than interpreting a single edge in isolation.
3. Find the unwrap through WETH
Switch to WETH to see the pool send WETH to Exploit Contract. Then switch to ETH to see the WETH contract send native ETH to the same contract.
Together, these paths show the unwrap. WETH and ETH are different assets, so filter and inspect them separately.
4. Confirm where ETH ends up
Follow the ETH edges to their destinations: most ETH goes to the transaction sender, while a small amount goes to the fee recipient.
You can now reconstruct the key path: XPEPE movement, WETH received and unwrapped, then ETH distributed.
What this transaction did
The transaction first moved about 49,498,286,779.1674 XPEPE from UniswapV3Pool into Exploit Contract. The contract then performed multiple XPEPE staking and withdrawal operations with TokenStaker, before returning XPEPE to the pool.
Later, the pool sent 0.680568466516036487 WETH to the contract. It unwrapped that into the same amount of ETH: 0.679568466516036487 ETH went to the transaction sender and 0.001 ETH to the fee recipient.
Notes
- An asset returning to its original address after a router, pool, or vault does not mean no business operation occurred. Check order and call context.
- ETH and WETH are different assets; wraps and unwraps link transfers between them.
- To identify the contract call that triggered a transfer, use Execution Trace.