# getRecentPrioritizationFees

> Returns per-slot prioritization fees paid recently, optionally scoped to a set of accounts.

Source: https://docs.constant-k.com/rpc/http/getrecentprioritizationfees/

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

- Transport: HTTP, JSON-RPC 2.0 `POST` to `https://rpc-newyork.constant-k.com/?api-key=YOUR_API_KEY` (New York) or `https://rpc-frankfurt.constant-k.com/?api-key=YOUR_API_KEY` (Frankfurt) or `https://rpc-amsterdam.constant-k.com/?api-key=YOUR_API_KEY` (Amsterdam). The key also works as an `x-api-key` header.
- Category: Fees & Blockhash
- Availability: All plans
- Rate limits: Free 5/s · Operator 50/s · Blade Runner 200/s · Nexus 500/s

## Parameters

`params` is a positional JSON array, in this order:

- `addresses` (string[], optional, max 128): 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.

## Result

- `result` (object[], optional): One entry per recent slot the node has fee data for, oldest first.
  - `slot` (integer, required): Slot this sample is for.
  - `prioritizationFee` (integer, required): 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.

## Example: Recent prioritization fees for two well-known mints

Request:

```bash
curl "https://rpc-newyork.constant-k.com/?api-key=YOUR_API_KEY" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getRecentPrioritizationFees",
    "params": [
      [
        "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
        "So11111111111111111111111111111111111111112"
      ]
    ]
  }'
```

Response:

```json
{
  "jsonrpc": "2.0",
  "result": [
    {
      "prioritizationFee": 908,
      "slot": 447947277
    },
    {
      "prioritizationFee": 0,
      "slot": 447947278
    },
    {
      "prioritizationFee": 209481,
      "slot": 447947279
    }
  ],
  "id": 1
}
```

_Long arrays in this example were trimmed._

## 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 `SetComputeUnitPrice` compute-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.