Skip to content

Solana method

getEpochInfo

Returns the current epoch, the slot index within it, and how far through it the cluster is.

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

This method has not been measured in this window.

It is scheduled but no observation has landed yet.

What it does

An epoch is roughly two days, about 432,000 slots. Stake activation, deactivation and validator rewards all happen on epoch boundaries.

The response gives absolute slot, slot index within the epoch, and the epoch length, which together tell you exactly how far through the epoch the cluster is.

Parameters

configObjectoptional
commitment and minContextSlot.

Returns

Object with epoch, slotIndex, slotsInEpoch, absoluteSlot, blockHeight and transactionCount.

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":"getEpochInfo"}'

As JSON-RPC

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "getEpochInfo"
}

Response

{
  "jsonrpc": "2.0",
  "result": {
    "absoluteSlot": 372145830,
    "blockHeight": 350412977,
    "epoch": 861,
    "slotIndex": 145830,
    "slotsInEpoch": 432000,
    "transactionCount": 412093847562
  },
  "id": 1
}

Things that bite

  • transactionCount is cumulative since genesis and includes vote transactions, which are the large majority of them.

Why it is measured

It returns several independent counters in one call, so a provider serving an internally inconsistent view of the chain shows it here.

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

24h window · generated 2026-08-24 17:26:48 UTC · 0 providers