What is a good Solana priority fee right now (and how to measure it)
There is no single "current Solana priority fee". The price that lands depends on which accounts your transaction writes: a hot pool can need a high price while the rest of the network clears at zero. Here is how to measure the right number for your transaction, and what we saw on mainnet today.
Short answer
Measure it for the account you write to and take the 75th percentile of recent blocks. On 2026-11-17, for swaps through the Raydium SOL-USDC pool, that was 10,000 micro-lamports per compute unit, which is 2,000 lamports (0.000002 SOL) for a 200,000 CU transaction, on top of the 5,000-lamport base fee. The same measurement without an account was 0. Your numbers will differ; the method is what carries over.
What the RPC actually reports
getRecentPrioritizationFees returns one number per block for the last ~150 blocks (about a minute). Each number is a floor: the lowest compute unit price paid by any transaction in that block that write-locked the accounts you passed. It is not an average and not what most transactions paid.
So read it this way: if the 75th percentile is 10,000, then in three of four recent blocks a transaction on that account landed while paying at most 10,000. Paying that much puts you at or above the cheapest successful transaction in most blocks.
Measure it in one command
npx github:blixvip/solana-priority-fee 58oQChx4yWmvKdwLLZzBi4ChoCc2fqCUWBkwMihLYQo2
Output from the public mainnet RPC, 2026-11-17 23:30 UTC:
150 slots (470718277-470718426), 1 account; 59.3% of slots had a non-zero fee
percentile micro-lamports/CU
min 0
p25 0
p50 3,227
p75 10,000
p90 10,000
p95 10,000
max 1,000,000
level micro-lamports/CU cost at 200,000 CU
low (p25) 0 0 lamports
medium (p50) 3,227 646 lamports
high (p75) 10,000 2,000 lamports
veryHigh (p95) 10,000 2,000 lamports
unsafeMax (p100) 1,000,000 200,000 lamports
cost excludes the 5,000 lamport base fee per signature.
Without an account, a minute later:
150 slots (470718292-470718441), no account filter; 0.0% of slots had a non-zero fee
...
p50 0, p75 0, p95 0, max 0
That zero is the trap: the unscoped answer is each block's lowest price, and somebody always lands for free. It says nothing about your pool.
Measure it with plain fetch
No library needed for the raw numbers:
const RPC = process.env.SOLANA_RPC_URL ?? "https://api.mainnet-beta.solana.com";
const POOL = "58oQChx4yWmvKdwLLZzBi4ChoCc2fqCUWBkwMihLYQo2";
const res = await fetch(RPC, {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({ jsonrpc: "2.0", id: 1, method: "getRecentPrioritizationFees", params: [[POOL]] }),
});
const { result } = await res.json();
const fees = result.map((r) => r.prioritizationFee).sort((a, b) => a - b);
const p = (q) => fees[Math.max(0, Math.ceil(q * fees.length) - 1)];
console.log(`${fees.length} slots; p50 ${p(0.5)}, p75 ${p(0.75)}, p95 ${p(0.95)} micro-lamports/CU`);
150 slots; p50 10000, p75 10000, p95 1000000 micro-lamports/CU
Which level to use
| Level | Percentile | When |
|---|---|---|
low | p25 | Not in a hurry; a retry is fine |
medium | p50 | Normal transfers and quiet pools |
high | p75 | A reasonable default for swaps |
veryHigh | p95 | A launch, a busy pump.fun curve, a liquidation |
unsafeMax | p100 | The highest floor seen; usually one outlier. Rarely worth it |
Use --ignore-zero when most blocks report 0 and you want the price among blocks where somebody did pay.
What a price costs
| Price (micro-lamports/CU) | At 200,000 CU | At 1,400,000 CU |
|---|---|---|
| 1,000 | 200 lamports | 1,400 lamports |
| 10,000 | 2,000 lamports | 14,000 lamports |
| 100,000 | 20,000 lamports | 140,000 lamports |
| 1,000,000 | 200,000 lamports (0.0002 SOL) | 1,400,000 lamports (0.0014 SOL) |
Formula: ceil(price × computeUnitLimit / 1,000,000) lamports, plus 5,000 per signature. Requesting fewer compute units cuts the fee as much as lowering the price.
What it does not cover
- Jito tips and staked senders. They help a transaction land too but are separate from the priority fee.
- Helius' getPriorityFeeEstimate. A different, Helius-only API with its own method. Its numbers will not match these.
- One node, one minute. A recently restarted node has fewer blocks, and 150 blocks is short. Re-measure right before you send.
Watch it over time
To be told when fees on your account spike, run the repo's Discord fee alert; to serve the number to several bots or a frontend, run the HTTP fee endpoint. To put the price into a transaction, see How to set a Solana priority fee in JavaScript.