Common Solana transaction errors and how to fix them
Solana processes thousands of transactions per second. When one fails, the error message can be cryptic. Below are the four most frequent errors, what causes them, and how to resolve them. Some errors waste your fee. Others reject the transaction before any SOL leaves your wallet.
Blockhash not found
This is the most common Solana error. Every transaction includes a recent blockhash - a cryptographic timestamp that expires after about 150 blocks (roughly 90 seconds). If you submit a transaction using an expired blockhash, the network rejects it with "Blockhash not found."
What triggers it. You constructed the transaction, waited too long to sign and send, or the network was congested and your RPC node fell behind. Wallets that cache blockhash aggressively can also produce this error.
Does it waste fees? No. The network rejects the transaction before processing it. No SOL is deducted.
How to fix it. Refresh your wallet or application. Most wallets (Phantom, Backpack, Solflare) fetch a fresh blockhash automatically when you retry. If you are building transactions manually, fetch a new blockhash from getLatestBlockhash before each submission. For automated scripts, implement retry logic that re-fetches the blockhash on failure.
Transaction simulation failed
This is a catch-all error. The network simulated your transaction and determined it would fail if executed. The message often includes a secondary clue: "instruction #X failed," "account not found," or "arithmetic overflow."
What triggers it. Common causes include: the token account you are sending from does not exist, the recipient's Associated Token Account has not been initialized, you are trying to close an account that still holds tokens, or a program instruction received invalid parameters. Slippage tolerance set too low on a swap can also trigger this.
Does it waste fees? No. Simulation happens before fee deduction. You pay nothing.
How to fix it. Read the secondary error text. "Account not found" means you need to create the recipient's token account first. "Slippage" means increase your slippage percentage or reduce the swap amount. "Instruction #X failed" points to a specific program call - check that all accounts passed to that instruction are correct. Most wallets show the simulation error; copy it and search the program's documentation.
Computational budget exceeded
Every Solana transaction has a compute unit limit - currently 200,000 CU by default. Complex operations (multiple token transfers, interacting with heavy programs) can exceed this budget.
What triggers it. You are doing too much work in one transaction. Examples: swapping through multiple pools in a single instruction, executing a batch of token transfers, or calling a program that performs heavy computation. The error message reads "Computational budget exceeded" or "exceeded CUs."
Does it waste fees? Yes. The transaction is executed partially and fails mid-way. The base fee is consumed. Priority fees are also lost.
How to fix it. Split the work into multiple transactions. Use ComputeBudgetProgram.setComputeUnitLimit to request a higher limit (maximum 1.4 million CU per transaction). If you are using a DeFi aggregator or wallet that builds complex instructions, check if the application supports batched transactions with higher budgets. For simple transfers, this error is rare.
Insufficient SOL for transaction fees
Solana requires a small SOL balance to pay fees. The minimum is the base fee (0.000005 SOL) plus any priority fee you set. If your wallet balance is below this threshold, the transaction fails before submission.
What triggers it. You drained your wallet to zero or very near zero. SOL is used for fees even if you are swapping tokens. A common scenario: you swap all but a few lamports, then cannot send the remaining tokens because there is no SOL to pay the fee.
Does it waste fees? No. The transaction is never submitted. No fee is charged.
How to fix it. Keep at least 0.01 SOL in your wallet for fees. If you are stuck, ask someone to send you 0.001 SOL or use a "SOL faucet" service. Some wallets now offer "fee delegation" where dApps cover the fee - look for that option. For automated scripts, always check the wallet balance before submitting.
A note on fee-wasting errors
Only "Computational budget exceeded" wastes fees. The other three errors reject before the network processes your transaction. If you see "Blockhash not found" repeatedly, your RPC provider may be slow. Switching to a different provider (Helius, Triton, QuickNode) often resolves it. Public RPC endpoints are free but unreliable for time-sensitive transactions.
Most errors are preventable by keeping your wallet updated, maintaining a small SOL buffer, and retrying quickly when a blockhash expires. If an error persists, copy the exact message and search the program's documentation or the Solana developer forum - someone has almost certainly solved it before.
Not financial advice. orymsolana.xyz publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.