TriportRPC

getMaxShredInsertSlot

POSThttps://api.triport.io

Returns the highest slot the node has observed after inserting shreds, before the slot is fully processed.

Solanasol_read_rpcfree+ — free 20 / basic 60 / pro 200 / business 600 RPS

getMaxShredInsertSlot returns the highest slot number that the node has seen after shred insert — that is, after the raw block fragments (shreds) for a slot have been received and written to the blockstore, but before the slot has been replayed and fully processed.

Because shreds arrive on the network ahead of full block processing, the value returned here is typically higher than getSlot (which reports the most recent processed slot). Use it as a leading indicator of how far the node has received block data, for example when monitoring ingest freshness or estimating how far behind processing is from the network tip.

Gotchas

  • This is not a confirmed or finalized slot. Data for the returned slot may still be incomplete or may not survive replay — never treat it as a slot you can safely fetch a full block for. Use getSlot or getFirstAvailableBlock for that.
  • The gap between this value and getSlot reflects shred-ingest lead time; it fluctuates and is not a fixed offset.

Parameters

None. The params array is empty.

optional
This method takes no parameters.

Response

Response fields

FieldTypeDescription
resultintegerHighest slot number seen after shred insert. May be greater than the latest processed slot from getSlot.

Errors

CodeMeaningWhen it happens
-32003Rate limit exceededMore 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.
-32601Method not recognisedThe method name was misspelled or is not in the Solana catalog.
-32602Invalid paramsA 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)

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


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

TypeScript SDK (@triport/sdk)

import { TriportClient } from "@triport/sdk";


const client = new TriportClient({ apiKey: process.env.TRIPORT_API_KEY! });


const maxShredSlot: number = await client.solana.getMaxShredInsertSlot();
console.log(`Max shred-insert slot: ${maxShredSlot}`);

Python (triport-sdk)

import os
from triport import TriportClient


client = TriportClient(api_key=os.environ["TRIPORT_API_KEY"])


max_shred_slot = client.solana.get_max_shred_insert_slot()
print(f"Max shred-insert slot: {max_shred_slot}")

Notes

  • Ingest lead indicator: compare this value with getSlot to gauge how far shred ingest is ahead of full processing. The two are related to getMaxRetransmitSlot, which reports the highest slot seen from the retransmit stage.
  • Not fetchable: the returned slot is pre-processing — do not pass it to block-fetching methods such as getBlock; use a confirmed slot instead.
  • Staging: the same request works against https://staging.api.triport.io for testing.