getMaxRetransmitSlot — Solana RPC Method

getMaxRetransmitSlot returns the highest slot that the node has seen from the retransmit stage. This is a low-level method used for monitoring node health and data propagation through the cluster.

Parameters

This method takes no parameters.

Request

curl -X POST https://api.mainnet-beta.solana.com \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getMaxRetransmitSlot",
    "params": []
  }'

TypeScript (@solana/kit)

import { createSolanaRpc } from "@solana/kit";

const rpc = createSolanaRpc("https://api.mainnet-beta.solana.com");
const maxSlot = await rpc.getMaxRetransmitSlot().send();

console.log(`Max retransmit slot: ${maxSlot}`);

Response

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

Common errors

This method has no parameters and rarely fails.

Performance

Returns a single number from the node’s internal state. Extremely lightweight.

FAQ

What is the retransmit stage? When a validator produces a block, it divides the data into shreds and sends them to the cluster. The retransmit stage is where nodes forward (retransmit) shreds they receive to other nodes in the cluster, ensuring data propagation.

How is this different from getSlot? getSlot returns the highest slot the node has reached at a given commitment level. getMaxRetransmitSlot returns the highest slot seen specifically in the retransmit pipeline, which is an internal processing stage.

When would I use this method? This method is primarily used for validator operations monitoring. If getMaxRetransmitSlot falls significantly behind getSlot, it may indicate issues with the node’s data propagation.

How does this relate to getMaxShredInsertSlot? Both are low-level node health indicators. getMaxRetransmitSlot tracks the retransmit stage, while getMaxShredInsertSlot tracks when shreds are inserted into the blockstore. Together they help diagnose which stage of block processing may be lagging.

Updated: 2026-10-19