get Recent Prioritization Fees
Returns per-slot prioritization fees paid recently, optionally scoped to a set of accounts.
getRecentPrioritizationFees returns the per-compute-unit price actually paid (via SetComputeUnitPrice) in each of the last ~150 slots. Account addresses, when included, scope the result to fees paid by transactions that locked those accounts as writable.
This is a real-time market signal, not a guarantee — contention on the accounts written to can change slot to slot.
Parameters
params is a JSON array, with values in this order: addresses.
Account addresses to scope the fee data to, base-58 encoded. Up to 128 addresses per call. Omit to get the general recent-fee data instead of an account-specific view.
128Result
One entry per recent slot the node has fee data for, oldest first.
Show each itemEach item
Slot this sample is for.
The per-compute-unit price, in micro-lamports, paid by the relevant transaction(s) in this slot. 0 means no priority fee was needed to land in that slot.
Notes
- A real call returns roughly 150 entries (the node's whole retained window); this example is trimmed to 3.
- The fee unit is micro-lamports per compute unit, matching the
SetComputeUnitPricecompute-budget instruction — multiply by the transaction's compute unit limit and divide by 1,000,000 to get the total priority fee in lamports. - Lots of zeros in the sample is normal: it means transactions touching those accounts landed without needing to outbid anyone that slot.