Transaction Failed When Creating a Solana Token? (Diagnostic Guide)

You clicked Create, signed the transaction in Phantom, and got an error. Before assuming the tool is broken, the first thing to do is read the actual error. Solana failures fall into about 6 distinct buckets, each with a specific fix. This guide walks through them in order of frequency.

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-library/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.

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.

---

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.

References

• Solana Transaction Reference — official protocol docs
• Solana Priority Fee Mechanics — when and how much to pay
• SPL Token Program Error Codes — full enumeration
• Solana Status Page — current network health
• Metaplex Token Metadata Program — for metadata-related errors
• Solscan — transaction explorer used in step 1
• QuickNode Solana Gas Tracker — current priority fee percentiles
• Helius RPC, QuickNode, Triton — paid RPC providers if Cause 5 keeps biting you