Getting Started
Quickly understand what happened in a transaction, from its outcome to its execution.
Skylens helps you understand a transaction's outcome and execution. Paste in a transaction hash to view balance changes, token transfer paths, contract calls, and on-chain state updates.
If you are not sure where to begin, follow the order below—or jump directly to the part you need.
What Skylens helps you do
- Confirm the outcome: Did the transaction succeed, and who ultimately gained or lost assets?
- Trace assets: Where did tokens come from, which contracts did they pass through, and where did they end up?
- Reconstruct calls: In what order did contracts run, and what did the key functions do?
- Verify state: Which balances, approvals, or contract variables were written on-chain?
- Investigate further: When needed, inspect the execution point in source code or bytecode.
Analyze a transaction in 5 steps
1. Start with the final asset outcome
Open Balance Changes. First look for balance changes on the sender, recipient, and key contracts. The positive or negative value in Change quickly shows who gained or lost an asset; use Before and After to confirm the final amount.
2. See how assets moved
Open Token Flow, choose the token you care about, and follow the connections through addresses and contracts. When you encounter a Router, Pool, or ETH/WETH wrap or unwrap, use the transfer order to understand each step.
3. Find the key contract call
Open Execution Trace and expand calls from the outermost level. Start with the target and function name, then inspect parameters, return values, or errors to find the call that moved assets or caused an issue.
4. Verify the final state update
Open State Changes and review variables and Storage Slots by contract. Compare Before and After to confirm whether the transaction changed a price, balance, approval, or other on-chain state.
5. Open the Debugger when needed
Once you have located a specific call and want to know why the code behaved that way, open Source Debugger. Continue with source code, the call stack, parameters, and variables; if source code is unavailable, switch to Bytecode Mode.
Start here
Open any transaction and start with Balance Changes. After confirming the final outcome, move to Token Flow, Execution Trace, State Changes, or Debugger as needed.