> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# getRecentPrioritizationFees | Solana

> The getRecentPrioritizationFees method returns a list of recent prioritization fees observed in the network. Solana via Chainstack.

# 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](/docs/solana-glossary#compute-units) 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.

<Note>
  Learn how to add priority fees to your transactions reading [Solana: How to use Priority Fees to unlock faster transactions](/docs/solana-how-to-priority-fees-faster-transactions).
</Note>

## 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.

<Warning>
  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.
</Warning>

## 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](/docs/solana-estimate-priority-fees-getrecentprioritizationfees) for a practical implementation guide.


## OpenAPI

````yaml openapi/solana_node_api/getRecentPrioritizationFees.json POST /9de47db917d4f69168e3fed02217d15b
openapi: 3.0.0
info:
  title: getRecentPrioritizationFees example
  version: 1.0.0
  description: This is an API example for Solana's getRecentPrioritizationFees.
servers:
  - url: https://nd-326-444-187.p2pify.com
security: []
paths:
  /9de47db917d4f69168e3fed02217d15b:
    post:
      tags:
        - query
      summary: getRecentPrioritizationFees
      operationId: getRecentPrioritizationFees
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                id:
                  type: integer
                  default: 1
                jsonrpc:
                  type: string
                  default: '2.0'
                method:
                  type: string
                  default: getRecentPrioritizationFees
                params:
                  type: array
                  default:
                    - - CxELquR1gPP8wHe33gZ4QxqGB3sZ9RSwsJ2KshVewkFY
      responses:
        '200':
          description: Recent prioritization fees details
          content:
            application/json:
              schema:
                type: object
                properties:
                  jsonrpc:
                    type: string
                  id:
                    type: integer
                  result:
                    type: array
                    items:
                      type: object

````