Your wallet can show an error even when the swap has landed. Check the original signature first, then use the status and error to decide what needs fixing before you submit another order.
In this article
Find the existing transaction before placing another order
Open the swap in your wallet or terminal history and follow its transaction link. Check that the explorer is showing the correct network and signature. Keep that page open while you investigate; the message in the trading interface may describe a submission or confirmation problem rather than the final on-chain result.
| What you find | What to do next |
|---|---|
| Confirmed success | Inspect the received token and destination account before placing another order. |
| Pending or unresolved | Continue checking the original signature. Do not assume a timeout cancelled it. |
| Confirmed failure | Read the error and failing instruction, then address that specific cause. |
| Quote or signing failed before submission | Investigate that step rather than treating it as a completed swap. |
An app error can appear while the transaction is still pending. Check History and the explorer before signing a replacement.
A transaction signature is an identifier, not a receipt
Solana's sendTransaction method returns when the RPC accepts the signed transaction. It does not wait for confirmation. Receiving a signature therefore does not establish that the swap executed.
The reverse also needs care. An empty result from getSignatureStatuses can reflect the scope of the lookup: by default it searches a recent status cache, while older searches require the history option. Similarly, getTransaction can return no result when a transaction is not found or has not reached the requested confirmation level. An unavailable lookup leaves the outcome unresolved.
This matters when contacting support. Send the original signature and explain which status you observed. Repeatedly signing new orders makes it harder to distinguish a delayed first attempt from a genuinely separate second trade.
Use the error to choose the fix
Error names identify different failure points. The Solana transaction pipeline reference separates fee-payer checks, blockhash validation, account loading and instruction execution. Increasing slippage is irrelevant to a missing fee balance or an expired transaction.
| Error or symptom | Check |
|---|---|
InsufficientFundsForFee | The fee payer's SOL balance and required fee. |
InsufficientFundsForRent | The balance needed for the account the transaction creates or changes. |
BlockhashNotFound | Transaction freshness and the RPC's view of the chain. |
InstructionError | The failing instruction and the program-specific error inside it. |
| No supported route | The exact token pair, amount and available markets. |
Jupiter's documented Swap Program errors include 6001 for exceeded slippage and 6024 for insufficient funds, including transaction or account costs. Those are program-specific codes from its older Metis documentation, not universal Solana error numbers. Record the provider and program as well as the number.
An expired transaction needs fresh transaction data
A normal Solana transaction contains a recent blockhash. Once it is too old, validators will not process that transaction. Delays while signing and inconsistent RPC views can both contribute to blockhash errors. Solana's confirmation guidance uses the returned lastValidBlockHeight to determine expiration rather than relying on a fixed number of seconds.
Check whether the original landed before rebuilding it. Expiration prevents future processing; it does not erase execution that already happened. Once the outcome is resolved, a replacement should use a new quote and fresh transaction data. Reopening an old signing request can preserve the very conditions that caused the failure.
Why a failed swap can still reduce your SOL balance
Solana charges a network fee for processing. Its fee documentation lists a base charge of 5,000 lamports per signature, with priority fees added where applicable. The fee is deducted before instruction execution and remains charged when execution fails. This is not the same as the intended token purchase completing.
Inspect the transaction's fee and token movements separately. A failed attempt can explain a fee deduction without explaining an unrelated balance change. Comparing only the wallet's total dollar valuation mixes transaction activity with changing token prices and can obscure what happened.
Change the condition that failed
For a slippage error, request a fresh quote and review the output and tolerance together. For an insufficient-balance error, check the spend amount and the separate balance used for costs. For a routing problem, verify the full mint address and whether that pair and amount have a supported market.
A priced quote is not necessarily executable. In Jupiter Swap V2, an empty transaction string can accompany valid pricing when transaction construction failed. Its error code must be interpreted with the router. These fields are useful evidence for support, rather than a reason to keep pressing the trade button.
Before another attempt, retain the signature, error, approximate time and app name. That is enough to begin a public-chain investigation. Wallet recovery phrases and private keys are not troubleshooting evidence. For the execution settings themselves, read slippage versus price impact.
Frequently asked questions
Do failed Solana transactions still charge a fee?
A transaction processed on-chain can fail during execution and still incur its network fee. A quote or simulation rejected before on-chain processing is a different case. Check the original signature and fee record rather than inferring the outcome from a lower wallet balance.
Can a swap go through after my wallet says it failed?
The app can report a confirmation problem while the transaction remains pending or has already completed. Open its original signature in an explorer and inspect the result before signing another order. An unresolved lookup is not proof of failure.
Why does Phantom say not enough SOL when I hold other tokens?
Your token balance and the balance used for network costs are separate. A normal Solana transaction needs a fee payer with SOL, even when the token being exchanged is USDC. Eligible gasless flows can handle the cost differently; check the fee disclosure for that particular transaction.
What does BlockhashNotFound mean?
The node cannot use the transaction's blockhash. It may be stale, or the RPC may have a different view of recent blocks. Resolve the original transaction's status before requesting fresh transaction data; increasing slippage does not repair a blockhash problem.
Questions or corrections? Contact the Talentre team.


