Skip to main content
POST
/
9de47db917d4f69168e3fed02217d15b
getRecentPrioritizationFees
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"
    ]
  ]
}
'
{
  "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 todayStart 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 fee in micro-lamports per compute unit paid by at least one transaction within the specified slot to achieve prioritized processing.
The node’s prioritization-fee cache stores data from the most recent 150 blocks. When account addresses are provided, the response reflects fees observed for transactions that locked all of the supplied accounts as writable simultaneously — not just any of them. If you omit the params array entirely, the response returns unfiltered samples across all transactions.

​
Use case

A practical use case for getRecentPrioritizationFees is to determine an appropriate priority fee for your transactions. By querying recent fees for the specific accounts your transaction will lock, you get a realistic picture of what competing transactions are paying. 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[]
Last modified on April 17, 2026