Transaction decoder
Paste a signature. See each instruction and CPI, which accounts were signers or writable, balance changes, compute units, the full log, and exactly why it failed.
How to read a failed Solana transaction
A transaction is a list of instructions executed in order. If any instruction returns an error, the whole transaction is rolled back and the RPC reports {"InstructionError": [index, error]}. The index tells you which top-level instruction failed; the error is either a named runtime error such as InvalidAccountData or {"Custom": 6001}, a code returned by the program.
Finding the program that failed
Programs call other programs (CPIs), so instruction #2 might fail deep inside a token transfer. The logs show the nesting: Program X invoke [1] is top level, [2] is a CPI, and the first line that reads Program X failed is the program that actually returned the error. This tool extracts that id and, for Anchor programs, the Error Code line with the human readable name.
What the account flags mean
- signer: the account’s private key signed the transaction (or a PDA signed via CPI).
- writable: the transaction may change the account’s lamports or data. Marking an account read-only that a program writes to causes ReadonlyDataModified.
- read-only: the account is only read. Programs and sysvars are always read-only.
Privacy
The signature is sent only to the RPC endpoint you configure, directly from your browser. Nothing is stored on this site.