getSlotLeaders

POSTSlots & EpochsAll plans

Returns the slot leader for each slot in a forward-looking range.

Try itSends a real request from your browser to the selected region.
POST
/

getSlotLeaders returns one leader identity per slot, starting at a given slot and running for limit slots — the multi-slot version of getSlotLeader. It supports planning around leader rotation ahead of time, such as choosing which leader to target next.

PlansAll plans
FreeIncluded
OperatorIncluded
Blade RunnerIncluded
NexusIncluded

Parameters

params is a JSON array, with values in this order: startSlot, limit.

1startSlotintegerrequired

First slot to return a leader for.

2limitintegerrequired

Number of slots to return leaders for, starting at startSlot.

Minimum: 1Maximum: 5000

Result

resultstring[]

One leader identity per slot in the requested range, in slot order.

Notes

  • The same identity repeating for several entries is normal: each leader gets a run of 4 consecutive slots before rotating.
  • startSlot must be within a range the node can still resolve a schedule for — asking too far past the current epoch boundary returns an error rather than a guess.