Decode, replay & mutate any transaction
Reconstruct the exact state a Solana transaction ran against, re-execute the real programs locally, then rewrite an account's fields to ask “what if?”
Decode
The full cross-program call tree, balance flows and compute per program — lookup tables resolved, accounts named via on-chain IDLs.
Replay locally
Rebuilds the world the transaction ran in — every account and program binary — and re-executes the real code in an embedded SVM.
Ask “what if?”
Rewrite a pool reserve, an oracle price, any account's bytes — then replay and diff to see what would have happened instead.
Time travel
Warp the clock a day, an epoch, a year — and watch vesting cliffs, cooldowns and auctions play out without waiting.
Instruction call tree
Instruction introspection
Program logs
Local replay
Scenario tests
svmscope replays the real programs against edited state, so you can assert what
should happen in each edge case — with no test harness to write. It starts you with a
suite auto-generated from this transaction; tweak the expectations, run them, and export the
suite to run in CI with svmscope test suite.json.
Advanced — edit account fields & add a custom scenario
Edit any field below, then Stage your changes and Add as test scenario to drop them into the suite above — or just Simulate once to preview.
See exactly what a transaction did, step by step
Paste any Solana transaction signature. You get a plain-English account of what happened, which step failed and why, and you can change a value and run it again.
What it did, step by step 0
Where the compute went
Program logs
Where did the compute go?
Paste any Solana transaction signature. Every BPF instruction it executed is attributed to programs, functions and syscalls and drawn as a flamegraph. Built your program yourself? Add its .debug file and every function gets its Rust name.