Case Studies
Solve onchain investigation tasks with evidence that others can verify
Start with a concrete question, then connect Skylens transaction analysis, contract storage, debugging, and Virtual TestNet capabilities to produce evidence-backed conclusions that other investigators can reproduce.
Choose an investigation
| Question | Primary product modules | Case study |
|---|---|---|
| Why did a transaction fail? | Execution Trace, Source Debugger | Diagnose the Root Cause of a Revert |
| Where did the assets come from and go? | Balance Changes, Token Flow, Execution Trace | Trace Asset Flows Through a Transaction |
| Which execution changed a target variable? | State Changes, Execution Trace, Source Debugger | Locate the Source of a State Variable Write |
| How do I inspect a critical call without source code? | Execution Trace, Bytecode Debugger | Debug an Unverified Contract |
| Where does a proxy actually store its state? | Proxy Storage, Storage Layout, State Changes | Analyze Proxy Contract Storage |
| How can I reproduce and verify a result in isolation? | Virtual TestNet, RPC, Foundry | Reproduce and Verify a Transaction in Virtual TestNet |
Suggested learning paths
- Transaction troubleshooting: diagnose a revert first, then continue with bytecode-level debugging.
- Asset and state auditing: trace asset flows first, then locate state-variable writes.
- Complex contract validation: analyze proxy storage, then reproduce the finding in a Virtual TestNet.
Every case follows the same progression: objective, context, questions, steps, evidence, and conclusion. Keep transaction hashes, block numbers, trace indexes, addresses, and raw values with your notes so another investigator can verify the result.