​
getRecentPrioritizationFees RPC Method

Returns a list of prioritization fees from recent blocks.

​
Method Information

Currently, a node’s prioritization-fee cache stores data from up to 150 blocks.

Parameters

array optional
An array of Account addresses

  • Maximum of 128 addresses
  • Addresses should be base-58 encoded strings

Account Address Consideration

If account addresses are provided, the response will reflect the fee to land a transaction locking all of the provided accounts as writable.

Code Sample

curl https://rpc.testnet.soo.network/rpc \
-X POST \
-H "Content-Type: application/json" \
-d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "getRecentPrioritizationFees",
  "params": [
    [
      "5ThJTCxpdn54bk3gBAWKZS4K9ogHEX56WooYbXQDnm3Q",
      "BESTc6u4kKPDrdAXHTKPgCm9bwBzDn2Nq9g4gk1Ld3P4"
    ]
  ]
}'

Response

{
  "jsonrpc": "2.0",
  "result": [
    {
      "slot": 369624,
      "prioritizationFee": 1000
    }
  ],
  "id": 1
}

​
Result Details

An array of prioritization fee objects, each containing:

  • slot: <u64>

    • Slot in which the fee was observed
    • Identifies the specific blockchain slot for the prioritization fee

  • prioritizationFee: <u64>

    • Per-compute-unit fee paid by at least one successfully landed transaction
    • Specified in increments of lamports

​
Important Notes

  • Prioritization-fee cache stores data from up to 150 blocks
  • Optional parameter allows filtering by specific account addresses
  • Maximum of 128 account addresses can be specified
  • Helps understand recent transaction priority fees
GetRecentPerformanceSamplesGetSignatureStatuses