Tools
Transaction Inspector
Paste any transaction signature and see what it did in plain English: status, fee, compute, every instruction, and who gained or lost what.
Open Transaction Inspector ↗Solana Transaction Inspector overview
Step by step
- Step 1Paste a signatureThe long base58 string from an explorer, a wallet's history or a Solstack result screen.
- Step 2Fetched from your networkDevnet or Mainnet, whichever the top bar is set to.
- Step 3DecodedA one-line summary, the fee and compute, each instruction explained, and every balance change.
When to use it
Use it to find out why a transaction failed, to check what a transaction did before trusting it, or to have a swap, transfer or mint explained without reading raw explorer output. No wallet is needed.
Summary
A confirmed transaction gets a one-line summary of what happened, such as a transfer, a swap or a token sold for SOL, with the number of signers and who paid the fee. A failed one shows which program rejected it and why. A failed Solana transaction moves no funds, but its fee is still charged.
The numbers
| Fee | What the fee payer paid, in SOL and lamports, including any priority fee. |
|---|---|
| Compute units | How much compute it used, against the limit it asked for. |
| Failed at | For a failed transaction: which instruction threw, and in which program. |
| Slot, time | When it landed, with the epoch and how long ago. |
What this transaction did
Every instruction is listed with the program it called and a plain explanation of what that instruction does, and its accounts are marked signer or writable. The instruction that failed is marked Threw; any after it are marked Never ran.
Balance changes
Net SOL and token movement per account, worked out from the balances before and after. This is the most reliable way to see who paid and who received, regardless of what the instructions appear to do.
Logs and raw data
The program logs are at the bottom. Copy raw JSON gives you the transaction exactly as the RPC returned it, and Open in Solscan opens it there.
“Not found”
Check the Devnet/Mainnet toggle first. Otherwise the transaction was dropped and never confirmed, or it's older than the RPC keeps history for. See the transaction lifecycle.
What it costs
Free. No signature is needed.
FAQ
What can I paste?
Any transaction signature.
Why 'not found'?
Wrong cluster, dropped, or aged out of RPC history.
What are balance changes?
Net SOL and token movement per account.
Is anything signed?
No.