getRecentPrioritizationFees

On Solana a base fee is paid in SOL for every signature, but during contention you also attach a priority fee — a price per compute unit that bumps your transaction ahead of others competing for the same accounts. getRecentPrioritizationFees reports the priority fees observed over recent slots, returning an array of { slot, prioritizationFee } entries you can use to size a compute-unit price that actually lands. Optionally pass the writable accounts your transaction will lock to scope the sample to that contention. Query it through TheRPC at https://solana.therpc.io/YOUR_API_KEY.

Use cases

• Pick a compute-unit price that gets a swap or transfer included even when the network is congested, such as during a busy Jupiter or Raydium trading window.
• Track the priority-fee trend for the specific writable accounts your transaction touches, since a hot AMM pool or token mint often demands a higher fee than the network average.
• Feed a dynamic fee estimator inside a sending service so the compute-unit price tracks live conditions instead of a hardcoded value.

Parameters

Response

Example request

1curl https://solana.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5  "jsonrpc": "2.0",
6  "id": 1,
7  "method": "getRecentPrioritizationFees",
8  "params": [
9    []
10  ]
11}'

Errors & troubleshooting

Common pitfalls

• Pass the base-58 writable accounts your transaction locks so the sample reflects contention for those exact accounts; an empty array returns a cluster-wide view that may understate the fee for a hot account.
• These are observed recent fees, not a promise of inclusion. Add headroom above the sampled values and re-check shortly before you sign, because conditions shift slot to slot at ~400ms cadence.

Supported networks

• Mainnet
• Devnet

See also

• getFeeForMessage
• sendTransaction
• simulateTransaction