Solana method

getSupply

Returns total, circulating and non-circulating SOL supply.

expensiveExpensive: scans a range or a large account set. Frequently restricted.Primary specification

How each provider handles it

This method has not been measured in this window.

It is in the catalogue but disabled, so nothing calls it.

What it does

Aggregates supply across the whole account set. `excludeNonCirculatingAccountsList` is worth passing: without it the node returns every non-circulating account address, which is a long list nobody usually wants.

Computing it requires touching a great deal of state, which is why it is expensive and frequently rate-limited.

Parameters

configObjectoptional: commitment, excludeNonCirculatingAccountsList.

Returns

Object under result.value with total, circulating, nonCirculating.

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":"getSupply","params":[{"excludeNonCirculatingAccountsList":true}]}'

As JSON-RPC

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "getSupply",
  "params": [{ "excludeNonCirculatingAccountsList": true }]
}

Response

{
  "jsonrpc": "2.0",
  "result": {
    "context": { "slot": 372145830 },
    "value": {
      "total": 604382919482938475,
      "circulating": 528374829384756,
      "nonCirculating": 76008090098182,
      "nonCirculatingAccounts": []
    }
  },
  "id": 1
}

Things that bite

Lamports, and well beyond 2^53. Parse with a BigInt.
Disabled by default on this platform: it is expensive enough that calling it on a schedule is not being a good citizen of someone else's infrastructure.

Why it is measured

Kept in the catalogue as a capability marker rather than a latency measurement, and left disabled.

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

30d window · generated 2026-08-24 17:26:54 UTC · 0 providers