getMaxShredInsertSlot — Solana RPC Method

getMaxShredInsertSlot returns the highest slot for which the node has received and inserted shreds into its blockstore. This is a low-level diagnostic method for monitoring node health and block data reception.

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": "getMaxShredInsertSlot",
    "params": []
  }'

TypeScript (@solana/kit)

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

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

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

Response

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

Common errors

This method has no parameters and rarely fails.

Performance

Returns a single number from internal node state. Extremely lightweight.

FAQ

What are shreds? Shreds are the smallest unit of block data in Solana. When a leader produces a block, it splits the block into shreds for transmission across the network. Receiving nodes reassemble shreds back into complete blocks.

What is the blockstore? The blockstore is the node’s local database of received block data. Shreds are written to the blockstore as they arrive, and complete blocks are assembled from the stored shreds.

When would I use this method? For validator operations and monitoring. If the shred insert slot falls behind the current slot, the node may have issues receiving or storing block data. Compare with getMaxRetransmitSlot and getSlot to identify bottlenecks.

How does this compare to getSlot? getSlot returns the highest processed slot at a commitment level. getMaxShredInsertSlot shows the highest slot for raw shred data storage, which is an earlier stage in the pipeline.

Updated: 2026-10-19