Solana validator network report

Solana Validator Leader Slots Report

Review how Solana leader slots relate to validator stake, epoch context, and low-latency infrastructure planning.

Data source

Solana Gossip + vote accounts

Updated Jul 13, 2026, 06:23 AM UTC

Schedule epoch

1,001

Leader slots

431,972slots

Leader validators

694validators

97.1%

Top leader

16,588slots

Figment

3.8%

Network intelligence

Network state, leader timing, and validator evidence in one report.

This panel adds live slot context, leader-window evidence, validator performance rows, and production samples to the existing reports without pretending unsupported data is already resolved.

leader window loadingperformance loading

Current slot

Leader feed loading · updated waiting

Observed slot time

Target 400 ms · epoch - complete

Transaction sample

- non-vote · - vote

Leader production sample

- scheduled · - skipped · skip -

Leader now

Resolving leader

Waiting for leader window

Slot

Window

Next different leader

Waiting for next leader group

Network activity evidence

Non-vote transactions

Vote transactions

Performance rows

Top leader-slot validators

Validators with the most scheduled leader opportunities in the joined snapshot.

Figment

3.8%

16,588 slots

Helius

3.7%

15,808 slots

Jupiter

12,824 slots

binance staking

2.7%

11,872 slots

Ledger by Figment

2.2%

9,620 slots

Bitwise Onchain Solutions

1.9%

8,244 slots

Everstake

1.8%

7,640 slots

Kraken 2

1.6%

7,072 slots

Staking Facilities | MEV 🔥

1.6%

6,696 slots

Galaxy

1.5%

6,348 slots

Top countries by leader slots

Country-level share of scheduled leader slots across geolocated validators.

Germany

151 validators · 25.5%

110,256 slots

Netherlands

105 validators · 18.7%

80,896 slots

United States

140 validators · 16.7%

72,284 slots

United Kingdom

34 validators · 10.9%

46,896 slots

Japan

73 validators · 5.8%

24,960 slots

Singapore

56 validators · 4.7%

20,276 slots

Canada

15 validators · 4.6%

19,968 slots

Lithuania

15 validators · 4.6%

19,892 slots

Ireland

8 validators · 2.1%

8,936 slots

Sweden

9 validators · 1.8%

7,796 slots

France

13 validators · 0.9%

3,952 slots

Hong Kong SAR China

19 validators · 0.8%

3,252 slots

Brazil

17 validators · 0.6%

2,408 slots

Switzerland

1 validators · 0.5%

1,952 slots

South Korea

1 validators · 0.3%

1,296 slots

Top cities by leader slots

City-level clusters of scheduled block production across geolocated validators.

Frankfurt am Main

91 validators · 19.9%

86,152 slots

Amsterdam

63 validators · 13.8%

59,732 slots

London

25 validators · 10.4%

44,772 slots

Singapore

56 validators · 4.7%

20,276 slots

Šiauliai

15 validators · 4.6%

19,892 slots

Lelystad

29 validators · 4.5%

19,480 slots

Toronto

12 validators · 4.5%

19,396 slots

Los Angeles

25 validators · 2.9%

12,608 slots

Ashburn

5 validators · 2.9%

12,444 slots

New York City

15 validators · 2.5%

10,764 slots

Offenbach

31 validators · 2.4%

10,244 slots

Eschborn

23 validators · 2.1%

9,104 slots

Ebara

8 validators · 2%

8,624 slots

Tokyo

59 validators · 2%

8,424 slots

Chicago

22 validators · 1.9%

8,016 slots

Key signal

Epoch context

Leader slots are evaluated inside the current epoch, so slot counts should be read together with epoch progress.

Key signal

Validator opportunity

Leader-slot counts show how many block-production opportunities a validator is scheduled for, not whether every opportunity performs equally.

Key signal

Network placement

Applications that react to Solana events can use leader context to reason about geography and network path quality.

What this report answers

This page explains why leader slots matter for Solana validators, RPC operators, low-latency applications, and trading systems. Use it to connect scheduled block-production opportunities with the live validator table.

How to read the data

The live rankings join validator directory data, vote accounts, Gossip metadata, and current leader-schedule counts. Because this is a joined current snapshot, leader-slot totals can differ slightly from the protocol epoch total when scheduled identities are no longer present in the current validator set.

How operators use it

Validator operators use leader-slot context to plan monitoring and incident response. Application teams use it to understand why distance to Solana leaders changes over time and why one fixed city is not enough for every slot.