Solana Priority Fee – Frequently Asked Questions

Here are the most commonly asked questions about Solana priority fees, answered with technical accuracy.

What is the difference between the base fee and a priority fee?

The base fee on Solana is a fixed cost of 5,000 lamports per transaction signature. It is always required and cannot be adjusted. The priority fee is an optional additional payment denominated in micro-lamports per compute unit. While the base fee pays for signature verification, the priority fee buys you ordering priority in the validator's scheduler queue.

Does a higher priority fee guarantee my transaction gets confirmed?

No — a higher priority fee significantly increases the probability that your transaction lands quickly, but does not guarantee it. If your transaction has other errors (expired blockhash, insufficient account balance, program logic failure), it will still fail regardless of the priority fee. Additionally, all transactions compete within the same thread on the scheduler, and priority is one of several factors.

How do I know what priority fee to set?

The best approach is to use the getRecentPrioritizationFees RPC method or a third-party API (Helius, QuickNode) to fetch real-time fee data. For most non-urgent transactions, the 50th percentile fee from the last 150 blocks is sufficient. For time-sensitive operations, use the 75th to 95th percentile.

What unit is the priority fee set in?

The priority fee is specified in micro-lamports per compute unit. One micro-lamport equals 0.000001 lamports. When you call ComputeBudgetProgram.setComputeUnitPrice({ microLamports: 100000 }), you are saying you will pay 100,000 micro-lamports (= 0.1 lamports) for each compute unit your transaction uses, up to the CU limit.

Can I set a priority fee on all types of Solana transactions?

Yes. Priority fees can be added to any Solana transaction by including the ComputeBudgetProgram.setComputeUnitPrice instruction. This applies to simple SOL transfers, SPL token transfers, program invocations, and complex multi-instruction transactions alike.

What happens if my priority fee is too low?

If your priority fee is below what most competing transactions are paying, your transaction may sit in the scheduler's buffer and eventually be dropped after the blockhash expires (approximately 150 slots / ~60 seconds). You would then need to resend the transaction with a fresh blockhash and ideally a higher fee.

Do wallets like Phantom handle priority fees automatically?

Some wallets, including Phantom, have implemented automatic priority fee management. Phantom calculates and applies priority fees to wallet-generated transactions and to dApp-generated transactions that meet their requirements. However, if your dApp explicitly sets a priority fee, your value takes precedence. Solflare automatically detects network load and adjusts fees accordingly.

What is the maximum priority fee I can set?

There is no hard protocol-level maximum on the micro-lamports per CU value you can set. Practically, fees above 10,000,000 micro-lamports/CU are very rarely needed. The maximum total priority fee per transaction is bounded by the CU limit (maximum 1.4 million CUs) and the price you set. For most use cases, 1,000,000 micro-lamports/CU is more than sufficient even during peak congestion.