Why Did My Solana Transaction Fail?
Paste a signature to see whether it worked, what it actually did, and why it failed if it did.
Common questions
My transaction failed. Did I lose the money I was sending?
No. A failed transaction changes nothing at all: no tokens moved, no SOL moved, no account was created. The one thing you did pay is the network fee, a fraction of a cent, because Solana charges for the work of processing it either way. Whatever you were sending is still in your wallet.
What does blockhash not found mean?
Your transaction took too long to reach the network and expired before it landed. Solana transactions are only valid for about a minute. Nothing happened and nothing was charged. Simply try again, and if it keeps happening the network is likely congested.
What is a custom program error?
A number raised by whichever program the instruction was aimed at. The same number means different things in different programs, so it is only meaningful once you know who raised it. We translate the SPL Token program's codes because that is what this site uses; for anything else we tell you the number and the program rather than guessing.
Why does it say it cannot name the error?
Because it genuinely cannot, and saying otherwise would be worse than useless. A confident wrong explanation sends you debugging the wrong thing, while the raw error at least looks like something you can search for. When that happens the raw error is shown in full so you can look it up or paste it to whoever is helping you.
It says the transaction was not found. What now?
Almost always the wrong network: switch the top bar between Mainnet and Testnet and try again. Failing that, very old transactions can be dropped by public RPC endpoints, which does not mean they did not happen. An explorer will usually still have it.
Some instructions say they could not be read. Is that a problem?
No. Solana's RPC parses instructions for a standard set of programs and returns raw data for everything else. When that happens we name the program that ran the instruction and stop, rather than guessing at what it did. It is normal on transactions involving DEXes and other third-party programs.
My deploy stopped halfway. Which step failed?
This will show you. A deploy on this site is several transactions in a row, so check the signature of the one that failed: the list of instructions shows exactly how far it got. If the token exists but the authorities were not revoked, the deploy console can retry just that step without charging you again.
The failure that is not a failure
The most common thing this tool reports is that nothing went wrong with your money. A failed Solana transaction is atomic: every instruction took effect or none did, so a failed transfer leaves the tokens where they were, and the only cost is a fraction of a cent for the network's work. Where it cannot name the cause it says so and shows the raw error, because a confident wrong explanation is worse than none.
Check where you are sending before you sign with Address Check, check a token before you trust it with the Rug Checker, and see everything outstanding before a launch with the Launch Checklist.