# getRecentPrioritizationFees
## getRecentPrioritizationFees — Recent prioritization fees
> Returns a list of prioritization fees from recent blocks to help estimate appropriate priority fees for transactions. The method returns data from up to 150 recent blocks stored in the node's prioritization-fee cache. When account addresses are provided, the response reflects the fees needed to land a transaction that locks all specified accounts as writable, helping estimate fees for transactions with account contention. This data is essential for applications that need to dynamically adjust priority fees based on current network conditions, ensuring transactions are processed quickly without overpaying. The fees are expressed in microlamports per compute unit, where 1 microlamport = 0.000001 lamports.\
> \*\*Parameters\*\*\
> \
> 0\. \`addresses\` (optional) — Optional list of account pubkeys (max 128). Returned fees are scoped to recent blocks that referenced any of these accounts.
```json
{"openapi":"3.0.3","info":{"title":"Solana RPC: getRecentPrioritizationFees","version":"1.0.0"},"tags":[{"name":"Fees","description":"Solana RPC fees method."}],"servers":[{"url":"https://public.rpc.solanavibestation.com","description":"Public endpoint (rate-limited, no auth)"},{"url":"https://lite.rpc.solanavibestation.com","description":"Lite tier"},{"url":"https://basic.rpc.solanavibestation.com","description":"Basic tier"},{"url":"https://ultra.rpc.solanavibestation.com","description":"Ultra tier"},{"url":"https://elite.rpc.solanavibestation.com","description":"Elite tier"},{"url":"https://epic.rpc.solanavibestation.com","description":"Epic tier"},{"url":"https://basic.swqos.solanavibestation.com","description":"Basic tier with Stake-Weighted QoS"},{"url":"https://ultra.swqos.solanavibestation.com","description":"Ultra tier with Stake-Weighted QoS"},{"url":"https://elite.swqos.solanavibestation.com","description":"Elite tier with Stake-Weighted QoS"}],"security":[{},{"AuthHeader":[]},{"URLParameter":[]}],"components":{"securitySchemes":{"AuthHeader":{"type":"apiKey","in":"header","name":"Authorization","description":"Pass `Authorization: ` on each request."},"URLParameter":{"type":"apiKey","in":"query","name":"api_key","description":"Pass `?api_key=` on the URL."}},"schemas":{"JsonRpcEnvelope":{"type":"object","required":["jsonrpc","id"],"description":"Base envelope of every JSON-RPC 2.0 response.","properties":{"jsonrpc":{"type":"string","enum":["2.0"]},"id":{"oneOf":[{"type":"string"},{"type":"integer"}],"description":"Echoed request id."}}},"JsonRpcErrorResponse":{"type":"object","required":["jsonrpc","id","error"],"description":"JSON-RPC 2.0 error response.","properties":{"jsonrpc":{"type":"string","enum":["2.0"]},"id":{"oneOf":[{"type":"string"},{"type":"integer"}]},"error":{"$ref":"#/components/schemas/JsonRpcError"}}},"JsonRpcError":{"type":"object","required":["code","message"],"description":"Structured JSON-RPC error.","properties":{"code":{"type":"integer","description":"Numeric error code per JSON-RPC 2.0 spec. Common values:\n- `-32700` Parse error\n- `-32600` Invalid Request\n- `-32601` Method not found\n- `-32602` Invalid params\n- `-32603` Internal error\n- `-32003` Unauthorized\n- `-32005` Too Many Requests\n- `-32015` Transaction version not supported\n"},"message":{"type":"string"},"data":{"type":"object","additionalProperties":true}}}},"responses":{"UnauthorizedError":{"description":"Authentication required or invalid.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/JsonRpcErrorResponse"}}}},"ForbiddenError":{"description":"Insufficient permissions for the request.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/JsonRpcErrorResponse"}}}},"TooManyRequestsError":{"description":"Rate limit exceeded for this tier.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/JsonRpcErrorResponse"}}}},"InternalServerError":{"description":"Unexpected server error.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/JsonRpcErrorResponse"}}}}}},"paths":{"/":{"post":{"operationId":"getRecentPrioritizationFees","summary":"getRecentPrioritizationFees — Recent prioritization fees","tags":["Fees"],"description":"Returns a list of prioritization fees from recent blocks to help estimate appropriate priority fees for transactions. The method returns data from up to 150 recent blocks stored in the node's prioritization-fee cache. When account addresses are provided, the response reflects the fees needed to land a transaction that locks all specified accounts as writable, helping estimate fees for transactions with account contention. This data is essential for applications that need to dynamically adjust priority fees based on current network conditions, ensuring transactions are processed quickly without overpaying. The fees are expressed in microlamports per compute unit, where 1 microlamport = 0.000001 lamports.\n**Parameters**\n\n0. `addresses` (optional) — Optional list of account pubkeys (max 128). Returned fees are scoped to recent blocks that referenced any of these accounts.\n","requestBody":{"required":true,"content":{"application/json":{"schema":{"type":"object","required":["jsonrpc","id","method","params"],"properties":{"jsonrpc":{"type":"string","enum":["2.0"],"description":"JSON-RPC protocol version."},"id":{"oneOf":[{"type":"string"},{"type":"integer"}],"description":"Request identifier echoed back in the response."},"method":{"type":"string","enum":["getRecentPrioritizationFees"],"description":"Must be `getRecentPrioritizationFees`."},"params":{"type":"array","description":"Positional parameters. Each item below corresponds to one position in the array, in order.","minItems":0,"maxItems":1,"items":{"anyOf":[{"title":"addresses (optional)","type":"array","items":{"type":"string","description":"Account pubkey, base-58."},"description":"Account pubkeys (max 128). Omit or pass an empty array for cluster-wide stats."}]}}}}}}},"responses":{"200":{"description":"Successful `getRecentPrioritizationFees` response.","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/JsonRpcEnvelope"},{"type":"object","required":["result"],"properties":{"result":{"type":"array","items":{"type":"object","properties":{"slot":{"type":"integer","format":"int64"},"prioritizationFee":{"type":"integer","format":"int64"}}}}}}]}}}},"401":{"$ref":"#/components/responses/UnauthorizedError"},"403":{"$ref":"#/components/responses/ForbiddenError"},"429":{"$ref":"#/components/responses/TooManyRequestsError"},"500":{"$ref":"#/components/responses/InternalServerError"}}}}}}
```
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.solanavibestation.com/developers/solana-rpc/http-methods/getrecentprioritizationfees.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.