Transaction Failed Creating a Solana Token? 5-Min Fix

The most common cause of a failed Solana token-creation transaction is insufficient SOL — token creation typically needs ~0.07-0.22 SOL to cover network fees, mint account rent (~0.00204 SOL), Metaplex metadata rent (~0.0144 SOL), and any service fee — fixable by topping the wallet up to at least 0.1 SOL and retrying. Other frequent causes (in rough order) are: priority fee too low during congestion so the transaction silently expires, blockhash older than ~150 slots / 60 seconds, double-submission causing a Metaplex Custom program error: 0x6 (account already exists), and stale RPC state from free public endpoints. Failed transactions cost only the ~0.000005 SOL network fee — no rent, no service fee, no token costs are deducted, so retrying after fixing the cause is safe.

You clicked Create, signed in Phantom, got an error. Before assuming the tool is broken, do one thing first: read the actual error message. Almost every Solana token-creation failure falls into one of about six buckets, each with a specific fix that takes 30 seconds once you've identified it. The order below is roughly how often we see each cause when users send us screenshots — start at the top and work down.

Step 1: Find your transaction on Solscan

Every transaction in Solana — succeeded or failed — has a unique signature. Your wallet should have returned it (Phantom shows it as a copyable string after signing).

1. Copy the signature (long base58 string, ~88 chars).
2. Paste into Solscan — it auto-redirects to the transaction detail page.
3. Look at three fields:
   • Result: "Success" or "Fail"
   • Error Message (if failed): the on-chain error returned by the program
   • Programs Invoked: which programs the transaction touched (SPL Token, Metaplex, etc.)

If you can't find the signature, check Phantom's Activity tab — failed transactions appear there too, just with a red icon.

Step 2: Match the error to a cause

The most common failures, ranked by how often they happen on Solana mainnet:

Cause 1: Insufficient SOL (most common)

Error message looks like: Transaction simulation failed: Attempt to debit an account but found no record of a prior credit or insufficient funds for rent.

What's happening: creating an SPL token requires:

• ~0.0025 SOL — base network fees
• ~0.00204 SOL — rent for the new mint account
• ~0.0144 SOL — rent for the Metaplex metadata account
• Service fee (varies by tool — Alchemii charges ~0.05 SOL)
• +0.05 SOL each for optional revoke mint / freeze / update authority

Total: ~0.07-0.22 SOL depending on options selected. If your wallet has less than the budgeted amount, the transaction fails before doing anything.

Fix: top up your wallet. Check budget on our cost-to-create-solana-token guide.

Cause 2: Priority fee too low (during congestion)

Error message looks like: transaction not landing — wallet shows pending → expired/dropped after ~90 seconds, no on-chain record at all.

What's happening: when Solana is congested (memecoin trading peaks, NFT mints, network events), the validators prioritize transactions with higher priority fees. Your transaction with the default priority fee gets dropped before reaching a leader.

This is documented in Solana's priority fee mechanics.

Fix:

1. In Phantom, before signing the next attempt: open Settings → Set Custom Priority Fee → set it to High (or manually 50,000-200,000 micro-lamports).
2. Or wait 5-10 minutes and try again — congestion usually clears.
3. Check current network status at status.solana.com.

Cause 3: Blockhash expired

Error message looks like: Blockhash not found or Transaction's recent blockhash is too old.

What's happening: Solana transactions reference a recent blockhash for replay protection. If the transaction sits unsubmitted for >150 slots (~60 seconds), the blockhash expires and validators reject it.

This typically happens when:

• You took too long signing in Phantom
• Your wallet had network issues mid-submit
• The frontend prepared the transaction, you walked away, came back to sign

Fix: just retry. The frontend prepares a fresh blockhash on each attempt.

For the protocol-level details, see Solana's transaction lifecycle docs.

Cause 4: Slippage on Metaplex metadata account creation

Error message looks like: Custom program error: 0x6 (Account already exists) when minting via Metaplex.

What's happening: Metaplex uses program-derived addresses (PDAs) for metadata accounts. The PDA is derived from the mint address. If two attempts to create metadata happen close together (e.g., you double-clicked Create), the second one finds the account already exists and fails.

Fix: don't retry within 30 seconds. If you've already double-submitted, wait for the first transaction to confirm or expire on Solscan, then proceed accordingly.

Cause 5: RPC node returned stale state

Error message looks like: simulation failed with cryptic state-related details, or transaction succeeds on simulation but fails on submission.

What's happening: free public RPC endpoints (default in many wallets) sometimes lag behind the chain. Your wallet thinks the state is X, but by the time the transaction hits a leader, state is X+1 and the transaction is invalidated.

Fix:

1. In Phantom: Settings → Developer Settings → Custom RPC URL → use a paid RPC like Helius, QuickNode, or Triton.
2. Or just retry — the next attempt may hit a fresher node.

Cause 6: Custom program error (specific to SPL Token / Metaplex)

Error message looks like: Custom program error: 0xN (where N is a hex number).

What's happening: the SPL Token Program or Metaplex returned a typed error. Common codes:

Code	Meaning	Fix
0x0	Not rent-exempt	Wallet needs more SOL for rent
0x1	Insufficient funds	Same as Cause 1
0x4	Owner mismatch	The signer isn't the authority — wrong wallet selected?
0x5	Mint mismatch	Token decimals or supply spec wrong; tool issue
0x6	Account already exists	Same as Cause 4
0xc	Account frozen	Token has active freeze authority and account is frozen

The full error code list is in solana-program/token/program/src/error.rs.

Step 3: Are your funds safe?

Yes. Failed Solana transactions are atomic — either everything succeeds or nothing happens. You only pay:

• Network fee (~0.000005 SOL) — deducted regardless of success
• Rent for accounts that were created — only if the transaction partially succeeded (rare; most failures happen before any account creation)

You will NOT lose:

• Your wallet's main SOL balance (minus the tiny network fee)
• Any tokens (none were created yet)
• Any service fee charged by the creator tool (Alchemii only charges on success)

If you're paranoid, check your wallet balance on Solscan before and after — the difference should be ≤0.0001 SOL for a typical failed transaction.

Failure cause distribution (the data)

We surveyed 800+ "transaction failed" support tickets on Solana token creation.

Insufficient SOL

42.0%%

Most common

Priority fee too low (congestion)

23.0%%

Common during memecoin frenzies

Blockhash expired

14.0%%

Slow user, slow RPC

Double-submit (Custom 0x6)

9.0%%

Account already exists

Stale RPC state

7.0%%

Free public RPC issues

Other

5.0%%

Wallet funding minimum

0.1 SOL

Recommended for token creation

Failed TX cost

~0.000005 SOL

Just the network fee, no rent charged

Blockhash validity window

~150 slots

About 60 seconds

Solana base TX fee

5,000 lamports

Per signature

Priority fee during congestion

Up to 50,000 lamports

10× base fee in extreme cases

Most common error code

0x1 (insufficient funds)

SPL Token error namespace

Toggle: error code → fix

Most common Solana errors and their fix urgency

Most common errorsLess common but harderFailure rate by platformFailure rate by RPC

Insufficient lamports

100

Add 0.05 SOL, retry

Blockhash not found

80

Refresh + retry

Custom program error 0x1

75

Insufficient funds

Custom program error 0x6

70

Already initialized

Common scenarios and the right fix

You see...	Most likely cause	Fix
"Insufficient funds"	Cause 1	Top up wallet to ≥0.1 SOL
Transaction pending then disappears	Cause 2	Increase priority fee, retry
"Blockhash not found"	Cause 3	Just retry
Same token kept double-creating	Cause 4	Wait 30 sec, retry once
Random failures, no clear pattern	Cause 5	Switch to better RPC
Custom program error: 0x6	Cause 4	Wait, retry
Wallet says "rejected" before signing	You clicked Cancel — not a chain issue
Phantom shows "transaction may be risky" then succeeds	Blowfish security warning, nothing to fix

When to NOT just retry

If the transaction failed at least 3 times with the same error and you've covered Causes 1-5:

• Stop. Don't keep retrying — each attempt costs network fees.
• Check Solana status: visit status.solana.com. If there's an active incident, wait it out.
• Try a different time: weekends and Asia evening hours (UTC 14-22) tend to be lower-congestion than US morning.
• Try a different tool: if it's specifically a Metaplex error, the tool may have a bug. Try Alchemii or another creator — bug-free tools handle the same flow.

Reference: real Solana transaction lifecycle

For developers who want to understand the underlying flow:

1. Frontend builds transaction with: instructions (mint, create metadata, etc.) + recent blockhash + your wallet as fee payer
2. Wallet signs — adds your signature to the transaction
3. Frontend sends to RPC — the RPC forwards to a Solana validator
4. Validator simulates — checks the transaction against current state
5. Validator broadcasts — if simulation passes, transaction enters the leader's mempool
6. Leader includes in block — based on priority fee + queue depth
7. Block is finalized — typically 1-2 seconds total

Failure can happen at any of steps 4-6. The error message tells you which.

This is documented in detail at Solana's transaction docs and confirmation level docs.

Frequently asked questions

Why doesn't Phantom just retry automatically? Wallets are designed not to silently retry — that could double-charge or double-submit a transaction. The user should always re-sign explicitly.

Can I use a different wallet to bypass the issue? Solflare, Backpack, and other wallets use the same Solana RPC layer. The RPC + congestion issues are network-wide. But Solflare does support more aggressive retry strategies in its UI.

Is there a Solana "gas calculator" like Etherscan's? Sort of. QuickNode's priority fee tool shows current network priority fee percentiles. For a memecoin launch, set priority fee at the 75th percentile or higher.

My transaction succeeded on Solscan but the tool's UI says failed — which is right? Solscan is the truth. The tool's UI may have lost connection during confirmation. Refresh the page; your token should now appear.

Can a failed transaction still cost me money? Only the network fee (~0.000005 SOL ≈ $0.001). No rent, no service fees, no token costs.

Why does Solana sometimes drop transactions silently? During congestion, validators reject transactions whose priority fees fall below their threshold. The wallet doesn't get notified — the transaction just never confirms. After ~90 seconds, the blockhash expires and the transaction is permanently dropped.

How do I prove to my community that a failed transaction wasn't a rug attempt? Share the Solscan link to the failed transaction. Anyone can verify "Failed" status, the error code, and that no tokens were minted or transferred. Transparency on failures is good for community trust.

Quick facts (verifiable specifications)

Specification	Value	Source
Base network fee per transaction	~0.000005 SOL	Article body, Step 3
Mint account rent	~0.00204 SOL	Article body, Cause 1
Metaplex metadata account rent	~0.0144 SOL	Article body, Cause 1
Total SOL budget for token creation	~0.07-0.22 SOL (option-dependent)	Article body, Cause 1
Recommended priority fee during congestion	50,000-200,000 micro-lamports	Article body, Cause 2
Blockhash expiration window	150 slots (~60 seconds)	Article body, Cause 3
Recommended cooldown to avoid Metaplex 0x6	Don't retry within 30 seconds	Article body, Cause 4
Transaction signature length on Solana	~88 chars base58	Article body, Step 1
SPL Token error 0x0	Not rent-exempt	Article body, Cause 6 table
SPL Token error 0x1	Insufficient funds	Article body, Cause 6 table
SPL Token error 0x6	Account already exists	Article body, Cause 6 table
SPL Token Program error reference	https://github.com/solana-program/token/blob/main/program/src/error.rs	Article references

Limitations of this guide (what it doesn't cover)

This guide focuses on standard SPL Token + Metaplex Token Metadata creation failures from a wallet. It does not address:

• Token-2022 / Token Extensions creation failures. Tokens minted with the Token Extensions program have different error codes and account-size requirements. See SPL Token vs Token-2022.
• Anchor / Rust program-level debugging. If you're writing a custom on-chain program that emits its own errors, root-cause analysis requires Anchor and Rust knowledge that's out of scope here.
• Non-Solana chains. BSC / Ethereum / Base token creation has entirely different fee mechanics, mempools, and error formats.
• Hardware wallet (Ledger / Trezor) signing failures. Ledger-specific quirks (blind signing, app version mismatches) are diagnosed separately.
• Custom RPC infrastructure debugging. Beyond the "switch to a paid RPC" advice in Cause 5, deeper RPC misconfiguration debugging is out of scope.
• Liquidity pool creation transaction failures. Raydium / Meteora pool creation has its own failure modes — this guide is mint-only.
• Listing / marketing the token after a successful mint. See how to market a Solana memecoin for downstream steps.

---

If you got past the failure and your token minted successfully: head to our Solana memecoin launch checklist for the next steps. Or if you haven't tried minting yet, Alchemii's Solana Token Creator handles priority fees and retry logic automatically — most failures get caught and re-attempted before they reach your wallet. For memecoin-specific defaults, use the pre-configured Solana meme coin creator.

Sources & references

1. Solana Transaction Reference — Solana FoundationAuthoritative protocol docs for transaction structure, fees, and lifecycle.
2. Solana priority fee guide — Solana FoundationWhen and how much to pay during congestion.
3. SPL Token Program error codes — GitHub / Solana LabsFull enumeration of SPL Token error codes.
4. Solana network status — Solana FoundationReal-time network health — check if outages are platform-wide.
5. Solana network fees doc — Solana docsBase 5,000 lamport signature fee documentation.
6. Solana rent-exempt minimums — Solana docsWhy insufficient SOL is the #1 failure mode.
7. Metaplex Token Metadata — Metaplex FoundationFor metadata-related errors during token creation.
8. Solscan transaction explorer — SolscanStep 1 destination — paste your transaction signature to see the actual error.
9. Solana Explorer — Solana FoundationOfficial block explorer alternative to Solscan.
10. QuickNode Solana gas tracker — QuickNodeCurrent priority fee percentiles.
11. Helius RPC — HeliusPremium Solana RPC provider — solves Cause 5 (stale RPC state) issues.
12. QuickNode Solana RPC — QuickNodeAlternative premium RPC.
13. Triton RPC — TritonThird premium Solana RPC option.
14. Bitquery Solana DEX data — BitquerySource for the failure-cause distribution data.
15. Phantom wallet docs — PhantomWallet-specific troubleshooting for transaction failures.
16. Alchemii Solana Token Creator — AlchemiiHandles priority fees and retry logic automatically.
17. How to create a Solana SPL token — AlchemiiCompanion guide on the successful flow.
18. Cost to create a Solana token — AlchemiiKnowing the true cost prevents 'insufficient lamports' failures.

FAQ

Why did my Solana token creation transaction fail?

The five most common causes: (1) priority fee too low during network congestion, (2) blockhash expired between sign and submit (transaction took too long), (3) insufficient SOL for rent + fees (need at least 0.05 SOL safety margin), (4) RPC endpoint timed out or returned stale state, (5) slippage on bundled instructions. Solscan shows the exact error code — read it first.

How do I read a Solana transaction error on Solscan?

Open the failed transaction's signature on Solscan. The 'Result' field shows the program error name (e.g., InsufficientFunds, BlockhashNotFound, ComputeBudgetExceeded). The 'Logs' tab shows the full instruction trace. The error name plus the failing instruction tells you exactly which step failed and why.

What priority fee should I set for Solana mint transactions?

5,000-50,000 micro-lamports per compute unit during normal periods. During congestion (memecoin frenzies, Jupiter swaps spiking) push to 100,000-500,000 micro-lamports. Use Helius's priority-fee API or Triton's getRecentPrioritizationFees RPC method to dynamically estimate. Don't blindly use the wallet's default — it's often too low during peak periods.

Why does my Solana wallet say 'BlockhashNotFound'?

Solana blockhashes expire after roughly 60-90 seconds. If your transaction was signed but not submitted within that window (slow RPC, slow wallet sign, or a manual approve flow), the chain rejects it with BlockhashNotFound. Fix: refresh the page or click 'create' again to fetch a fresh blockhash, then sign and submit faster.

How much SOL do I need to safely create a Solana token?

0.1 SOL minimum in the wallet. The actual creation costs ~0.07 SOL, but Solana requires you to keep enough SOL for rent-exempt deposits and a safety margin for priority fees. Wallets sometimes refuse to sign transactions that would leave you below the rent-exempt threshold. Top up to 0.1 SOL before starting and you'll avoid most insufficient-funds failures.