Free score in seconds. No sign-up, no wallet. Mint addresses and links from DexScreener, Jupiter, pump.fun, Birdeye, Solscan and GMGN all work.

Home › Blog › Why a failed Solana transaction still charged a fee

Why a failed Solana transaction still charged a fee

November 15, 2026 · 4 min read · by the Rugsight team

If a Solana transaction fails, the transfers it tried to make are not applied. The signature fee still is. That is expected behaviour on Solana, not a special penalty and not a sign that funds were taken beyond the fee. This guide explains what is reversed, what is not, and how that looked on a recorded mainnet transaction from 15 November 2026.

For the broader reading order (signature, status, fee, then nets, then programs), see how to read a Solana transaction. To paste a signature into Rugsight, use the transaction explainer.

Have a mint in front of you? Check it while you read.

Free score in seconds. No sign-up, no wallet. Mint addresses and links from DexScreener, Jupiter, pump.fun, Birdeye, Solscan and GMGN all work.

No mint handy? Open a token our scanner just checked (free, live data):

The fee is for processing, not for success

A Solana transaction is included in a block after the network has executed it, or attempted to. The fee payer (account index 0) pays a fee in SOL for that work: a base fee per signature, plus any priority fee the transaction requested through the Compute Budget program. The runtime takes that fee whether meta.err is empty or not.

What you usually care about is the other half: token and SOL transfers, account creations, wraps, swaps and approvals are rolled back on failure. preBalances and postBalances (and the token-balance equivalents) for those accounts match again, except for the fee payer's SOL, which is lower by the fee. If you only glance at a wallet's SOL and see a small drop, it is easy to miss that the large swap never happened.

This is different from a successful swap that also charged a fee. In the success case, the fee is one line next to a real movement. In the failure case, the fee can be the only lasting balance change.

A recorded failed swap

On 15 November 2026 at 00:38 America/Fortaleza, signature 5cTzUFTgbDbQMU49ZLjT3QtR3q2qhKKrhsiUnCfK3eypHqfCQGHndTsCC2ur7K8SscCGrLT6McWc4ByYwcukAhgy landed and failed. The fee payer was 8szGUCBxWT5xBf2uwT41494TJ81UY6wjQYoZV86yUFip. The fee was 0.000012893 SOL. The explorer and Rugsight both report the same error: instruction 8 failed with Custom(3) from a program this explainer does not label (program id B2TE7rYv4QosU4cLSB639H4bMTdLTqtwJcomhE4oCGda). A second unrecognised program, ZERor4xhbUycZ6gb9ntrhqscUcZmAbQDjEAtCf4hbZY, also appears in the trace.

The outer instructions show what the transaction attempted: it created associated token accounts, transferred 0.720999992 SOL into a wrapped-SOL account, called syncNative, invoked Jupiter (JUP6LkbZbjS1jKKwapdHNy74zcZ3tLUZoi5QNyVTaV4), and sent a 0.000001 SOL transfer. Because the transaction failed, those wrap and swap effects were not left in place. The durable fact is the fee and the error.

Rugsight's summary for this signature is: the transaction failed, instruction 8 failed with custom program error 3 from an unknown program, and a fee of 0.000012893 SOL was still charged. Unknown programs are listed as unknown. The page is /tx/5cTzUFTgbDbQMU49ZLjT3QtR3q2qhKKrhsiUnCfK3eypHqfCQGHndTsCC2ur7K8SscCGrLT6McWc4ByYwcukAhgy. The same signature is on Solscan.

The explainer does not suggest a fix. Custom(3) is a program-defined code. Without that program's error map, the honest statement is the code, the instruction index, and the program id.

What to look at on the explorer

  1. Result / status. Failed (sometimes shown with the InstructionError index).
  2. Fee. Still present. This is the SOL that left the fee payer.
  3. Balance changes. The fee payer's SOL should be down by about the fee. Other accounts should not show a completed swap or a completed wrap. If they do, you may be looking at a different, successful transaction.
  4. Logs and the failing instruction. The index in meta.err (instruction 8 in the example) points at the instruction that returned the error, counting outer instructions from zero. Inner instructions can make this feel off-by-one if you are counting a flattened list; prefer the explorer's instruction index or the InstructionError field itself.
  5. Priority fee. A Compute Budget "set compute unit price" instruction raises the fee without changing the outcome of a failed swap. A failed transaction with a high priority fee still pays that fee.

If you expected a large token movement and only the fee changed, the transaction did not land as a swap. Retrying is a new transaction with a new signature and a new fee.

What this does not mean

A failed transaction that charged a fee is not, by itself, a drained wallet. The usual leftover is the fee only. It is also not evidence that a token is a honeypot; a program can fail for many reasons (slippage, a missing account, an expired blockhash, a custom error). Sellability is a token-level question, covered in how to check if you can sell.

Rugsight's explainer reports the failure, the fee, and any decoded error it knows. It does not estimate "what you would have received" on a failed swap, and it does not simulate a retry.

FAQ

Why did I pay a fee if my Solana swap failed?

Solana charges the fee payer for processing the transaction, not for the swap succeeding. Transfers, wraps and swaps are rolled back when meta.err is set. The signature fee (and any priority fee) is not.

Was my wrapped SOL left in a token account after a failed swap?

On the recorded example above, the wrap and the Jupiter call were part of the failed transaction, so those balance changes were not kept. After a failure, check postBalances and postTokenBalances (or the explorer's balance-change table). If the wrap had been in an earlier successful transaction, that WSOL would still be there; that would be a different signature.

How do I see the exact fee on a failed Solana transaction?

Read the fee field on the transaction, or the fee payer's SOL change. On 15 November 2026, signature 5cTzUFTgbDbQMU49ZLjT3QtR3q2qhKKrhsiUnCfK3eypHqfCQGHndTsCC2ur7K8SscCGrLT6McWc4ByYwcukAhgy charged 0.000012893 SOL. Rugsight prints that amount next to the error on /tx.

Can Rugsight tell me how to fix a Custom(3) error?

No. A custom program error is defined by the program that returned it. The explainer reports the instruction index, the code, and the program id when it has them. It does not attach a suggested fix.

Check a token now

Free score in seconds. No sign-up, no wallet. Mint addresses and links from DexScreener, Jupiter, pump.fun, Birdeye, Solscan and GMGN all work.

Or start from BONK, WIF, all popular tokens or the new-token feed. See what the paid report contains in the free sample.

Related tools

Transaction explainer
Paste a transaction signature to read what it did in plain language, with a risk check on the tokens involved.
Solana error code lookup
Decode custom program errors, Anchor errors and JSON-RPC errors into the program and error name.
Instruction reference
Look up Solana program instructions and decode an instruction discriminator.

All Rugsight tools →

More from the blog