Overview
Understand Skylens's core modules and choose the right investigation path for a transaction or contract.
Skylens is an on-chain analysis and debugging platform for smart contract developers, security researchers, and auditors. It turns a transaction from an opaque hash and a set of logs into an investigation you can follow: confirm the outcome, reconstruct asset movement, inspect contract calls, verify state changes, and move into source or bytecode debugging when necessary.
What Skylens helps answer
When you investigate a transaction, you usually need answers to a few questions:
- Did the transaction succeed? Who sent it, who received it, and how much gas did it cost?
- Where did assets ultimately move, and which contracts did they pass through?
- In what order did contracts call each other, and what were the key function parameters and return values?
- Which Storage did the transaction actually change, and where did an error or revert occur?
Skylens brings these into one investigation flow, so you do not need to jump between a block explorer, logs, ABIs, source code, and debugging tools.
Product modules
Transaction
Transaction analysis
Reconstruct execution, follow assets, and pinpoint the cause of an issue.
- Execution Trace
Reconstruct the call tree and inspect parameters, return values, and errors.
- Token Flow
Visualize how tokens move between addresses and contracts.
- Debugger
Map each execution step to source code, call stack, and variables.
- Bytecode Debugger
Inspect EVM instructions, Stack, Memory, and Storage without source code.
Address
Address and contract analysis
Move from contract code and read-only calls to the underlying storage.
- Sources
Review verified source, ABI, compiler metadata, and implementations.
- Read Contract
Call view functions directly to inspect public contract state.
- Storage Layout
Locate variables by type, byte range, and Storage Slot.
- Proxy & Namespaced Storage
Resolve implementations and decode proxy or EIP-7201 storage.
Virtual TestNets
Isolated test networks
Reproduce on-chain scenarios safely against realistic chain state.
- Create a Fork
Start an isolated, resettable network from a chosen chain and block.
- Configure Test State
Adjust account balances, block time, and other environment state.
- Connect via RPC
Use the RPC URL with wallets, scripts, and development tools.
- Replay & Verify
Replay transactions, inspect the result in Skylens, and reset anytime.
A recommended investigation path
- Choose a transaction to analyze.
- In Overview, confirm the transaction status, participants, and net asset impact.
- Use Token Flow to understand the path assets took.
- Find key contract calls and parameters in Execution Trace.
- Use State Changes to verify persistent state writes.
- Enter Debugger when you need to locate the cause in source or bytecode.
ABI, contract source, compiler information, and Source Maps affect how well Skylens can decode function names, variables, and source locations. Even when that information is incomplete, raw Trace data, Storage Slots, and Bytecode Mode still provide useful evidence.
Next, read Getting Started and complete an investigation with a real transaction. Refer to the Glossary whenever a product or EVM term is unfamiliar.
Case studies
If you already have a specific question, start with one of these investigation cases:
