Skip to content

Solana method

getSlot

Returns the highest slot the node has reached at the requested commitment.

cheapCheap for a provider to serve — no state is read, or one key is.Primary specification (opens in a new tab)

How each provider handles it

3 providers

Provider support for getSlot on Solana
ProviderStatusSuccessMedian
Solana FoundationSupported100.0%14 ms
PublicNodeDegraded98.5%26 ms
TatumDegraded87.8%30 ms

Success excludes calls the provider does not implement — an optional method a provider declines to offer is a capability fact, not a failure, and is never scored as one.

Over time

Median latency per minute. Gaps are periods with no measurement, drawn as gaps rather than joined across — a line through missing data invents a measurement that was never taken.

Logarithmic scale — each gridline is ten times the one below it. Click a provider in the legend to hide it.

What it does

A slot is a scheduled ~400ms window in which a leader may produce a block. Slots advance whether or not a block is produced in them, so the slot number is Solana's clock rather than a count of blocks.

The commitment parameter changes the answer substantially. `processed` returns the newest slot the node has seen, `confirmed` one that has a supermajority of votes, and `finalized` one that is more than 31 blocks deep. Between `processed` and `finalized` there is normally a gap of several seconds.

Parameters

configObjectoptional
commitment (processed, confirmed or finalized) and minContextSlot.Default: finalized

Returns

u64 — the slot number.

Try it

Runnable as written, against a keyless public endpoint. Nothing here needs an API key.

Request

curl -s https://api.mainnet-beta.solana.com \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"getSlot","params":[{"commitment":"finalized"}]}'

As JSON-RPC

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "getSlot",
  "params": [{ "commitment": "finalized" }]
}

Response

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

Things that bite

  • Comparing a processed slot from one provider against a finalized slot from another measures the difference between two commitment levels, not between two providers. Every measurement here pins the same commitment for exactly that reason.
  • Slots are skipped when a leader fails to produce. A gap in slot numbers is normal and is not missing data.

Why it is measured

It is the primary Solana freshness signal, and at roughly 400ms per slot the chain moves fast enough that a provider a few slots behind is visibly behind.

Called every 30 seconds per endpoint, with jitter so the fleet does not hit a provider in lockstep.

1h window · generated 2026-10-08 17:52:47 UTC · 3 providers