HostNexFlow › Guides › Solana priority fees
Solana priority fees: why your transaction lands, or doesn't
Solana doesn't charge a base fee the way Ethereum does. It charges a tip. When blocks fill up, validators pick transactions by that tip — and your swap either makes it in or it silently never does.
Every Solana transaction pays two things: a tiny fixed base fee of 5,000 lamports (0.000005 SOL, effectively nothing) and an optional priority fee — the part that actually decides whether you get into the next block. There is no gas price in the Ethereum sense; there is a bid.
The two knobs: compute limit and compute price
Priority fees are set with two instructions inside the transaction itself:
SetComputeUnitLimit declares how much compute (work) your transaction might need. It's a ceiling, not a charge — you only pay for what you use, but you must budget enough or the transaction fails with "exceeded CUs."
SetComputeUnitPrice is the bid: micro-lamports per compute unit. The priority fee you actually pay is roughly compute unit price × compute units used. Validators running full blocks sort by this price, highest first.
The one-sentence model: the base fee gets your transaction into the building; the priority fee decides which floor of the building it gets. When a block has more transactions than room, the highest bidders go first and everyone else waits — or expires.
About to trade something volatile? Check it first
A fair priority fee can't save you from a honeypot. Read the token before you bid.
Why transactions fail under congestion
When a hot launch or a market move floods the network, blocks fill in milliseconds. Three failure modes dominate:
"Blockhash not found" — your recent blockhash expired. Solana blockhashes live about 60–90 seconds; if your transaction sat in a queue too long, it's dead. Resubmit with a fresh blockhash.
"Exceeded CUs" — your compute unit limit was too low for what the transaction actually did. Raise the limit (you're not charged for unused budget).
Silent non-landing — your priority fee was below the clearing price. No error, no confirmation, no money moved. This is the one that tricks people: the swap "did nothing" because it was never included.
How to set a sane fee
Let the wallet estimate. Phantom and most modern wallets query recent fees and bid slightly above median. For ordinary swaps this is correct almost always.
Check a priority-fee tracker during volatility. When fees spike, the tracker shows the current clearing price; bid a little above it. Overpaying on every transaction wastes SOL over time; underpaying during a pump means you miss the move entirely.
Jito bundles for guaranteed inclusion. Jito is a block-engine that lets you attach a bundle of transactions with a direct bribe to validators, bypassing the public mempool ordering. It's how market makers and launch snipers guarantee landing — and why a retail swap can still lose to a bundle during chaos.
Frequently asked
Does Solana have a base transaction fee?
Not in the Ethereum sense. Every transaction pays a tiny fixed base fee of 5,000 lamports (0.000005 SOL) plus an optional priority fee. The priority fee is the part that actually competes for block space.
What is a compute unit price on Solana?
It's the bid, in micro-lamports per compute unit, set via SetComputeUnitPrice. Validators order transactions by this price when blocks are full, so a higher bid lands faster during congestion.
Why did my Solana transaction fail with 'Blockhash not found'?
Your transaction's recent blockhash expired before it landed — Solana blockhashes live about 60–90 seconds. It's not a fee problem; resubmit promptly with a fresh blockhash. Repeated failures usually mean congestion priced you out, not expiry.
How high should my Solana priority fee be?
For normal swaps, a wallet's auto-estimate is usually fine. During congestion, check a priority-fee tracker and bid slightly above the median. Overpaying wastes SOL; underpaying during a volatile move means your tx never lands.
Measured data — what our scanner sees
Priority fees price compute units — the same on-chain state our grades read on every token.
From our latest published safety snapshot — 2,001 Solana tokens dated 2026-08-17 to 2026-09-16 — 75.6% had mint authority renounced, 90.0% had freeze authority renounced, and grades split A 1,533 / B 415 / C 53. Every row carries its snapshot date; the full dataset is CC BY 4.0 at nexflowscan.com/data/, and the scoring method is at nexflowscan.com/methodology/.
Sources & further reading
- Solana docs: Fees — Base fee, prioritization fee, and compute-unit pricing — the primary reference.
- Solana docs: Transactions — Blockhash validity and the transaction lifecycle.
- Jito — Block engine for bundles and low-latency submission.
- Solana Explorer — Inspect the compute-unit price and fee on any transaction.