Leader schedule
Leader schedule names the validator leading each slot, in order, starting from the slot you request.
Leader Slot API
The leader rotates slot by slot, and the order is redrawn every epoch.
That makes it something you check as you go, not a fact you note once and set aside.
Get your API keyEpoch —
— countries
Leader
—
Producing blocks live
In every response
Each record names the leader for that slot, their stake weight, and their estimated city, country, and network operator. A Solana epoch runs about 432,000 slots; keeping the leader schedule, each leader's location, and reference ping current across all of them takes a dedicated pipeline. We maintain it, so you read the map instead of building one.
Leader schedule names the validator leading each slot, in order, starting from the slot you request.
Stake weight is drawn from the current epoch: validators with more stake tend to appear in the leader schedule more often over time.
Leader location comes from the validator's estimated city, country, coordinates, and network operator, so you can place each leader before you connect.
Reference ping comes from ERPC's seven observation regions (Frankfurt, Amsterdam, New York, London, Tokyo, Singapore, Sydney), each measured independently, so a slower or missing reading from one region does not mean a leader is unreachable.
Calling the method
getLeaderSlots slots into the same request shape you already send, with no separate SDK and no new client to install.
Method
getLeaderSlotsEndpoint
https://edge.erpc.global?api-key=<YOUR_API_KEY>Each call returns 100 leader slot records and costs 420 tokens.
Start a free trial, issue an API key, and test low-latency RPC, Geyser gRPC, Direct Shreds, and SLV AI right away. Measure first, then expand into Dedicated Nodes, VPS, or Bare Metal when your production path is clear.