getLeaderSchedule

getLeaderSchedule is a Solana JSON-RPC method that returns the leader schedule for an epoch — the deterministic plan that says which validator produces blocks in each slot of the chain that settles SOL. The result maps every leading validator's identity pubkey to the list of slot indexes it owns within the epoch, or null if the schedule is unavailable. Pass any slot in the target epoch (or omit it for the current epoch) and an optional config with commitment or identity to filter to a single validator. Send it as a JSON-RPC 2.0 POST with positional params to https://solana.therpc.io/YOUR_API_KEY.

Use cases

• Find out exactly which slots a given validator is scheduled to lead during the epoch, for capacity planning or dashboards.
• Predict the leader for an upcoming slot so you can route a Solana transaction toward that validator's TPU ahead of time.
• Filter with the identity option to one validator to size how many leader slots it holds this epoch.

Parameters

Response

Example request

1curl https://solana.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5  "jsonrpc": "2.0",
6  "id": 1,
7  "method": "getLeaderSchedule",
8  "params": [
9    250000000,
10    {}
11  ]
12}'

Errors & troubleshooting

Common pitfalls

• The returned slot indexes are offsets within the epoch, not absolute slots — add the epoch's first slot (from getEpochSchedule / getEpochInfo) to get global slot numbers.
• The first positional argument is any slot inside the target epoch, not an epoch number; omit it entirely to get the current epoch's schedule.

Supported networks

• Mainnet
• Devnet

See also

• getSlotLeaders
• getBlockProduction
• getEpochSchedule