Stop overpaying
If the station is calm, a tiny priority fee — or none — lands just as well. Many wallets default far higher than needed.
Bulletin · loading
Feewind turns the chain's recent priority-fee readings into a forecast you can act on: how windy it is, where the gusts are, and what compute-unit price would have cleared the last 150 slots.
01 · Live station
Priority fees on Solana are local: they depend on which accounts a transaction writes to. Choose a busy program or pool — or paste any account — to see its own weather.
—
| Percentile | All slots | Non-zero slots |
|---|---|---|
| — | ||
µ-lamports per compute unit. "All slots" includes the many slots whose cheapest landed transaction paid nothing.
SOL price: loading…
02 · Regional fee map
Compare every station side by side. Feewind reads them one after another (about one per second) to stay gentle on the shared public RPC.
03 · Method
getRecentPrioritizationFees returns, for roughly the last 150 slots, the lowest priority fee any transaction paid to land — optionally only among transactions that write to the accounts you name.
Each slot becomes a bar on a log scale, because fees range from zero to millions of µ-lamports. Colours follow the wind scale below.
Percentiles show what share of recent slots a given price would have matched or beaten. We compute them twice: over all slots, and over only the slots that had a non-zero floor.
The 75th percentile (nudged up when many slots have a non-zero floor) picks a level on a fee "Beaufort scale" from Calm to Storm, and the tiers translate into a lamport cost for your compute budget.
04 · Uses
If the station is calm, a tiny priority fee — or none — lands just as well. Many wallets default far higher than needed.
Point the station at a busy pool or program during a launch and watch its local fee floor climb while the rest of the network stays calm.
Use the percentile tiers as a starting point for a dynamic compute-unit price instead of a hard-coded number.
Transactions not landing? Compare your price with the 75th–90th percentile for the accounts you write to.
The calculator converts a CU limit and price into lamports, SOL and USD using a live SOL price.
Seeing calm network-wide while one pool storms is the clearest lesson in why Solana fees are per-account.
05 · Field guide
Every Solana transaction pays a base fee of 5,000 lamports per signature (0.000005 SOL). On top of that it can pay an optional priority fee, which tells the leader "process me first". Priority fees are set with two Compute Budget instructions: a compute-unit limit (how much work the transaction may do) and a compute-unit price in micro-lamports (millionths of a lamport) per unit.
priority fee (lamports) = CU limit × CU price (µ-lamports) ÷ 1,000,000
Note that the fee is charged on the limit you request, not on what the transaction actually uses. Setting a tight, realistic limit is the single easiest way to pay less for the same priority. A transaction can request at most 1.4 million compute units; if you set no limit, the runtime assumes 200,000 per instruction.
Solana runs transactions in parallel unless they write to the same account. That means congestion is local too: a hot memecoin pool can be in a storm while a simple SOL transfer elsewhere sails through. The scheduler orders transactions that contend for the same writable accounts by priority, so what matters is the fee level of your accounts, not the whole network. That is why Feewind lets you pick a station.
The RPC reports the minimum fee paid by any transaction that landed in each slot. In most slots at least one transaction paid nothing extra, so the floor is zero. A zero floor does not mean nobody paid — it means paying nothing was enough to get in at least once. When the floor rises above zero in many slots, it is a sign of real competition. That is why the percentage of non-zero slots is one of the best single indicators on this page.
Some traders also send tips through block-engine services to bundle transactions. Tips are separate transfers and do not appear in these readings. Feewind only shows the protocol's own compute-unit priority fees.
06 · Questions
No. The tiers describe what would have matched the cheapest landed transaction in recent slots. Landing also depends on your RPC, network path, blockhash age and the exact accounts you touch. Treat them as a starting point.
Without accounts, the node reports the cheapest transaction in each whole block — and almost every block contains some transaction that paid nothing extra. Busy pools and programs are far more informative.
A millionth of a lamport. A lamport is a billionth of a SOL. A price of 100,000 µ-lamports per CU on a 200,000-CU transaction costs 20,000 lamports, or 0.00002 SOL.
The busiest writable account your transaction touches — usually the pool (AMM) account for a swap, or the program's global state for a launchpad. Program IDs also work, but a specific pool usually gives the sharpest local reading.
No. Tips are paid as normal transfers to tip accounts and are not part of the compute-budget priority fee the RPC reports.
Only when you ask, or every 15 seconds with auto-refresh on. It stops while the tab is hidden, to be kind to the shared public RPC.
No. Feewind is read-only and never asks for a wallet, signature or key.
solana-rpc.publicnode.com) and cover only about the last 150 slots it has seen. A different node may report slightly different values.