Guide

Solana priority fees explained

Most Solana transfers cost a tiny fixed base fee and nothing more. During busy periods — a popular NFT mint, a memecoin launch, or a network spike — thousands of transactions compete for limited block space. A priority fee is the optional tip you attach so validators prefer your transaction over others. This guide explains how priority fees work, what you actually pay, and what to do when a payment seems to vanish because it never landed.

Base fee vs priority fee

Every Solana transaction pays a base fee of 5,000 lamports (0.000005 SOL) per required signature. That fee is mandatory and predictable. Our transaction fees guide covers base fees and why micropayments like 0.001 SOL are practical on Solana.

A priority fee is separate. You offer extra lamports — priced per compute unit your transaction consumes — so block producers schedule your transaction ahead of competing ones. Think of it as express shipping: the package still has a standard postage rate, but you pay more to jump the queue.

Simple SOL transfers use very few compute units and rarely need a priority fee. Complex instructions — swaps on a DEX, minting NFTs, closing multiple token accounts — burn more compute and are more likely to stall without one when the network is hot.

Compute units and micro-lamports

Solana measures work in compute units (CUs). Each instruction in your transaction consumes CUs up to a per-transaction cap (currently 1.4 million CUs on mainnet). Wallets and dApps estimate how many CUs a transaction will need and set a compute unit limit accordingly.

The priority fee is expressed as micro-lamports per compute unit. One micro-lamport is one-millionth of a lamport. The formula is:

priority fee (lamports) = compute units used × micro-lamports per CU ÷ 1,000,000

Example: 200,000 CUs at 10,000 micro-lamports/CU costs 200,000 × 10,000 ÷ 1,000,000 = 2,000 lamports (0.000002 SOL) on top of the base fee. Even aggressive priority settings during congestion usually total well under a cent in USD — still cheap compared to Ethereum gas spikes, but not zero.

What you see in a block explorer

On Solscan or similar explorers, open a transaction and look for Priority Fee or Compute Units Consumed in the details panel. Our Solscan walkthrough shows where status, amounts, and fees appear. A failed or dropped transaction may show zero priority fee because it never executed — only landed transactions burn the full fee.

When you actually need a priority fee

You can ignore priority fees most of the time. Reach for them (or let your wallet auto-add them) when:

  • Network congestion — social media is buzzing about a mint or airdrop and simple transfers start failing or hanging.
  • Time-sensitive actions — sniping a listing, claiming a limited reward, or submitting a bid before a deadline.
  • Complex transactions — Jupiter swaps, liquidity adds, program deployments, or batched instructions that use hundreds of thousands of CUs.
  • Repeated simulation failures — your wallet says "transaction may fail" or drops the tx before you even sign.

A plain 0.001 SOL transfer to a game or merchant almost never needs manual tuning. Garden Dice and similar micropayment flows use a single signature and minimal compute. If those fail, the cause is usually insufficient SOL, wrong network, or a cancelled approval — not priority fees. See our transaction failed hub before cranking fees.

How wallets handle priority fees

Modern Solana wallets increasingly set priority fees automatically:

Phantom

Phantom can add a dynamic priority fee based on recent network activity. In Settings, look for transaction priority or fee preferences. During congestion, "Aggressive" or similar options raise micro-lamports/CU so your tx competes harder. For routine sends, the default is usually fine.

Solflare

Solflare exposes fee tiers in the send confirmation screen on busy days. You may see low / medium / high priority choices with estimated total cost. Pick higher only when a transfer keeps timing out.

Backpack

Backpack follows similar patterns — base fee plus an optional priority component shown before you approve. If you batch actions in one transaction, the CU estimate and priority line item may be larger than a bare SOL transfer.

dApps can also set priority fees in the transaction they ask you to sign. You do not configure this manually; you only approve or reject the total fee shown. If a site quotes an unusually high fee, cancel and verify you are on the real domain — phishing sites abuse urgency, not just fake URLs.

Dropped, expired, and stuck transactions

A transaction can fail in three confusing ways:

  1. On-chain failure — the transaction landed but a program returned an error (insufficient funds, slippage exceeded, etc.). You pay the base fee (and any priority fee consumed). The signature exists on-chain with a Failed status.
  2. Dropped before inclusion — validators never picked your transaction within its recent blockhash window (~60–90 seconds). No signature on-chain; your SOL never moved. Retry with a higher priority fee or wait for quieter blocks.
  3. Stuck in "pending" — your wallet submitted the tx but RPC or indexers lag behind. Check the signature on an explorer. If it is missing after two minutes, treat it as dropped and retry. Our confirmation time guide explains processed vs finalized and RPC delays.

Never retry blindly. If a payment actually landed, sending again doubles your spend. Always search the first signature in our tx lookup tool or Solscan before approving a second attempt.

Practical tips (without overpaying)

  • Start with defaults. Wallets tune priority fees from live network data. Only bump priority after a genuine drop.
  • Retry off-peak. Congestion often clears in minutes. Waiting beats paying 10× priority on every click.
  • Keep extra SOL. Base fee + priority fee + transfer amount must fit in your balance. "Insufficient SOL" errors ignore priority math — see insufficient SOL fixes.
  • Split complex batches. One huge transaction with dozens of instructions hits CU limits and needs hefty priority. Smaller txs can be cheaper overall.
  • Use a reliable RPC. A slow RPC makes healthy transactions look stuck. Wallets let you switch endpoints in advanced settings if confirmations lag.

Priority fees vs Ethereum gas (quick comparison)

Ethereum L1 uses an auction: you bid gwei per unit of gas and pay for gas used. Solana splits the model: a fixed base fee per signature plus an optional per-CU priority tip. Solana block times stay near 400 ms; priority fees influence ordering within the next slots, not whether blocks exist. That is why everyday Solana use stays cheap while Ethereum L1 micropayments are often impractical. Layer-2 chains change that calculus, but native Solana remains the path for sub-cent wallet-native games and tips.

Practice: a fee you can actually see

Priority fees shine during storms; calm weather is the right time to learn what normal looks like. Send a tiny mainnet payment and inspect the fee breakdown:

  1. Fund a wallet on mainnet — first Solana payment walkthrough.
  2. Approve a 0.001 SOL Garden Dice roll and copy the signature from your wallet.
  3. Open it on Solscan. Note base fee, any priority line, and total lamports burned.
  4. Compare with a busy-day swap screenshot online — the CU and priority numbers will be much larger.
Beat roll of 4 — 0.001 SOL Free demo first

Related guides and tools