getMaxRetransmitSlot — Solana JSON-RPC

Status: Available

Returns the highest slot the node has observed coming out of its retransmit stage.

POSThttps://triport.io/sol

Network: Solana
Scope: sol_read_rpc
Auth: x-token: $TRIPORT_API_KEY (or Authorization: Bearer)
Rate limit: free+ — free 20 / basic 60 / pro 200 / business 600 RPS sustained · up to 1200 burst; Burst capacity

Endpoint and plans: Solana RPC endpoint.

Request

cURLJavaScriptPython

curl https://triport.io/sol \
  -H "Authorization: Bearer $TRIPORT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getMaxRetransmitSlot",
    "params": []
  }'

const res = await fetch("https://triport.io/sol", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.TRIPORT_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getMaxRetransmitSlot",
    "params": []
  }),
});
const data = await res.json();
console.log(data);

import os


import requests


resp = requests.post(
    "https://triport.io/sol",
    headers={
        "Authorization": f"Bearer {os.environ['TRIPORT_API_KEY']}",
        "Content-Type": "application/json",
    },
    json={
        "jsonrpc": "2.0",
        "id": 1,
        "method": "getMaxRetransmitSlot",
        "params": [],
    },
)
data = resp.json()
print(data)

Response

JSON

Example

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": 348392041
}

getMaxRetransmitSlot returns the highest slot seen from the retransmit stage — the point in the validator's turbine pipeline where shreds received from peers are forwarded on. It is a single slot number reflecting how far the node has progressed in propagating blocks across the cluster.

This is a low-level diagnostic metric, primarily useful for observing a node's ingest/forwarding progress rather than for application data. To track the slot a node will actually serve confirmed reads from, prefer getSlot; to see how far shred insertion has advanced, compare with getMaxShredInsertSlot.

Gotchas

The value is node-local and reflects pipeline state, not network finality — it is not a confirmed or finalized slot and should not be used as a read floor for fetching block data.

It advances continuously as the node receives shreds; do not cache it.

Parameters

None. The params array is empty.

——optional

This method takes no parameters.

Response

Response fields

Field	Type	Description
`result`	integer	The highest slot seen from the retransmit stage.

Errors

Code	Meaning	When it happens
`429`	Rate limit exceeded	More than your tier's RPS for `sol_read_rpc` (free 20 / basic 60 / pro 200 / business 600); a burst up to 2× is allowed before throttling. Rejected before the RPC layer, so this is a plain HTTP error with `Retry-After` — not a JSON-RPC envelope.
`-32601`	Method not recognised	The method name was misspelled or is not in the Solana catalog.
`-32602`	Invalid params	A non-empty `params` array was sent — this method accepts no parameters.

See the shared errors reference for the full error envelope and the error.data fields.

Examples

JavaScript (fetch)

JavaScript

const res = await fetch("https://triport.io/sol", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.TRIPORT_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    jsonrpc: "2.0",
    id: 1,
    method: "getMaxRetransmitSlot",
    params: [],
  }),
});


const { result } = await res.json();
console.log(`Max retransmit slot: ${result}`);

Notes

Diagnostic, not finality: this reports turbine pipeline progress. For the slot the node serves reads from, use getSlot.
Related metric: getMaxShredInsertSlot reports the highest slot seen after shred insertion; comparing the two shows how retransmit and insert stages are tracking relative to each other.
Moving target: the value climbs as shreds arrive — re-query rather than caching it.