getRecentPrioritizationFees | Solana

POST /9de47db917d4f69168e3fed02217d15b

getRecentPrioritizationFees

cURL

curl --request POST \
  --url https://nd-326-444-187.p2pify.com/9de47db917d4f69168e3fed02217d15b \
  --header 'Content-Type: application/json' \
  --data '
{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "getRecentPrioritizationFees",
  "params": [
    [
      "CxELquR1gPP8wHe33gZ4QxqGB3sZ9RSwsJ2KshVewkFY"
    ]
  ]
}
'

200

{
  "jsonrpc": "<string>",
  "id": 123,
  "result": [
    {}
  ]
}

Solana getRecentPrioritizationFees method

The getRecentPrioritizationFees method returns a list of recent prioritization fees observed in the network. These prioritization fees represent the per-compute-unit fees paid by transactions to gain priority over other transactions in the same block.

The prioritization fee is optional and can be attached to a transaction to increase its likelihood of being included in the next block. A transaction can be prioritized over other transactions with lower or no prioritization fees by paying a higher prioritization fee.

Learn how to add priority fees to your transactions reading Solana: How to use Priority Fees to unlock faster transactions.

Get your own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, Twitter, Google, or Microsoft account.

Parameters

• array — an array of base-58 encoded public key strings representing Solana account addresses, with a maximum of 128 addresses.

Response

The response is an array of objects, where each object represents a prioritization fee observed in a recent slot (block). Each object has the following properties:

• slot (u64) — the slot where the transactions associated with the prioritization fees were processed.
• prioritizationFee (u64) — the per-compute-unit fee in micro-lamports. With no params, this is the minimum prioritization fee observed across all transactions in the slot. With params, this is the maximum across the supplied accounts of each account’s minimum writable-account fee for that slot — that is, the floor fee for the most expensive of your accounts in that slot.

The node’s prioritization-fee cache stores data from the most recent 150 blocks.

How the account filter works

For each slot in the cache, the node:

1. Looks up the minimum fee paid by any transaction that wrote to each supplied account that slot.
2. Returns the maximum of those per-account minimums.

The returned value is a floor — the cheapest fee that landed while writing to the most expensive of your accounts that slot — not a typical or competitive fee.

If you omit the params array entirely, the response returns the minimum prioritization fee per slot across all transactions. Because every slot contains 0-priority-fee vote transactions, this floor is effectively 0 in every slot and is not useful for fee estimation.

Pass writable state accounts (pool state accounts, reserves, user token accounts) — not program IDs. Programs are typically executable and read-only, so they are not present in the per-account writable fee map. Passing a program ID like a Jupiter or Raydium program returns near-empty data and gives a misleading picture of recent fees.

Use case

A practical use case for getRecentPrioritizationFees is to set a floor for your priority fee. By querying recent fees for the specific writable accounts your transaction locks, you see the cheapest competing transactions that landed touching those accounts. To produce a competitive bid, take a high percentile (p95) or the maximum of non-zero values over the 150-slot window and multiply by an urgency factor.

See also Estimate priority fees with getRecentPrioritizationFees for a practical implementation guide.

Body

application/json

id · integer · default: 1

jsonrpc · string · default: 2.0

method · string · default: getRecentPrioritizationFees

params · array

Response

200 - application/json

Recent prioritization fees details

jsonrpc · string

id · integer

result · object[]