# Solana Priority Fee Tracker

> Solana priority fee tracker: compute-unit prices paid by landed transactions in each slot at four percentiles, the price for hot accounts and how fees spike.

Markdown copy of https://voltfincrypto.com/apps/solana-priority-fee-tracker

**Question:** What priority fee does a Solana transaction need to land right now?

- Kind: Dashboard in Voltfin Vantage
- Topic: [Solana](https://voltfincrypto.com/topics/solana)
- Chains: Solana
- Status: Planned. The data is not published yet, so this page states no figure; each figure will open its receipt when it is.

A Solana transaction pays a fixed base fee per signature and can add a priority fee: a price per compute unit, in micro-lamports, paid to the block's leader to schedule it sooner. When many transactions compete for the same accounts, such as a popular pool during a token launch, the price needed to land rises for those transactions while others stay cheap. This dashboard reads the prices that landed transactions actually paid, slot by slot.

Use it to set a compute-unit price that lands now, to tell whether a slowdown is network-wide or limited to a few busy accounts and to see how quickly fees fall after a spike. Every percentile is computed from the transactions in specific slots and pinned to those slots, with a receipt.

## Blueprint

### Now

The compute-unit prices recent slots paid, network-wide and for hot accounts.

- **Median compute-unit price** (micro-lamports per CU): The median price per compute unit paid by landed non-vote transactions over the last 150 slots.
- **75th percentile price** (micro-lamports per CU): The 75th percentile compute-unit price over the last 150 slots: a price that lands ahead of most of the queue.
- **95th percentile price** (micro-lamports per CU): The 95th percentile compute-unit price over the last 150 slots: what the most urgent transactions paid.
- **Hot-account median** (micro-lamports per CU): The median price paid by transactions writing to the most contended accounts over the last 150 slots.
- **Prices by slot** (micro-lamports per CU): The 25th, 50th, 75th and 95th percentile compute-unit price of each recent slot, so a spike shows the slot where it starts.
- **Most contended accounts**: The accounts written by the most transactions in recent slots, with the median and 95th percentile price paid to touch them and the program that owns them.

### History

How priority fees moved over the last day, week and month.

- **Median price in the period** (micro-lamports per CU): The median compute-unit price paid by landed non-vote transactions over the selected period.
- **Transactions with a priority fee** (%): The share of landed non-vote transactions in the selected period that set a compute-unit price above zero.
- **Priority fees paid by day** (SOL): Total priority fees paid each day in SOL, set against base fees.
- **Priority price by day** (micro-lamports per CU): The median and 95th percentile compute-unit price of each day, from every landed non-vote transaction.

Filters: Period (Last day, week or month).

## How it will be measured

- Compute-unit prices are read from each landed non-vote transaction's compute budget instructions: SetComputeUnitPrice for the price and SetComputeUnitLimit for the requested limit.
- For each slot, the 25th, 50th, 75th and 95th percentile price per compute unit is taken over landed transactions, with transactions that set no price counted at zero.
- Each transaction's priority fee in lamports is its meta.fee minus the base fee for its signatures, which matches the price times the requested compute limit.
- Hot-account percentiles use only transactions that write to the most contended accounts in each slot, since Solana prices congestion per account.
- Tips paid to bundle auctions are transfers, not part of the fee, and are shown apart; every percentile carries a receipt with its slots.

## Data it needs

- `gas_blocks` (to build): Base fee, priority fee percentiles, gas used and gas limit for each block on fee-market chains, for a near-live gas tracker.
- `chain_fees_daily` (to build): Fees paid per chain per day in the native token: base fee and priority fee percentiles, total fees, and the share burned where the chain burns fees.
- `native_prices_daily` (to build): Reference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time.
- Source: ComputeBudget program (ComputeBudget111111111111111111111111111111) SetComputeUnitPrice and SetComputeUnitLimit instructions per transaction
- Source: meta.fee and signature count of each landed non-vote transaction, per slot
- Source: The writable accounts of each transaction, to find the most contended accounts per slot
- Source: Transfers to bundle tip accounts, kept apart from fees

## Questions

### What priority fee should I set on Solana?

When the network is quiet, a low compute-unit price is usually enough. When the accounts your transaction touches are busy, match at least the median price recent slots paid for those accounts. The dashboard shows both the network-wide and the hot-account percentiles.

### How is the Solana priority fee calculated?

It is the compute-unit price you set, in micro-lamports, times the compute-unit limit you request, not the units your transaction ends up using. Requesting a tighter limit therefore lowers the fee at the same price.

### Why is my Solana transaction not landing?

Common causes are a priority fee below what competing transactions pay for the same accounts, an expired blockhash or a compute limit too low for the work. The hot-account tiles show whether the accounts you touch are in demand at that moment.

### Do priority fees go to validators?

Yes. Priority fees go in full to the leader that produces the block, while half of each base fee is burned. Some validators share their priority fees with stakers through separate programs.

### What is a local fee market?

Solana's scheduler orders transactions that write to the same accounts by price, so congestion on one account raises fees only for the transactions touching it. Transactions elsewhere in the same block can still land cheaply.

## Glossary

- **Compute unit**: Solana's measure of the computation a transaction uses; each transaction requests a limit.
- **Micro-lamport**: One millionth of a lamport, the unit in which compute-unit prices are set.
- **Write lock**: A transaction's claim on an account it modifies; transactions writing the same account cannot run at the same time.
- **Bundle tip**: A payment to a bundle auction's tip account for ordered inclusion, separate from the protocol fee.

## Related apps

- [Solana Network Stats: TPS, Fees and Active Wallets](https://voltfincrypto.com/apps/solana-network-stats)
- [Pump.fun Token Launches and Graduations per Day](https://voltfincrypto.com/apps/pump-fun-token-launches)
- [Ethereum Gas Tracker](https://voltfincrypto.com/apps/ethereum-gas-tracker)
- [Solana Validator Count and Stake Concentration](https://voltfincrypto.com/apps/solana-validator-count)
- [Solana vs Ethereum: Fees, Activity and Revenue](https://voltfincrypto.com/apps/solana-vs-ethereum)
- [Solana Staking Yield (APY) and SOL Staked](https://voltfincrypto.com/apps/solana-staking-yield)

Build it in Voltfin Studio: https://app.voltfincrypto.com/signup?next=%2F