schedulers.watch

Solana block schedulers, compared each day

schedulers.watch compares the block schedulers that Solana validators run: Jito, JitoBAM, Harmonic, Rakurai, Raiku and Vanilla. It also splits each scheduler by validator client: Agave, Frankendancer and Firedancer.

A scheduler decides which transactions a leader puts in its block, and in which order. The choice changes the fees and tips that a block earns, how fast the block fills, and how long the slot takes.

The site shows the adoption of each scheduler by stake and by validator count, how blocks fill over the slot, how closely the order of transactions follows fees and tips, the observed block time, the revenue per block, and where oracle updates land in a block. Every chart can show one validator against its scheduler group.

The data updates each day. All numbers come from public sources: Firedancer validator reports, Trillium, Ghost shred data, Dune and Solana mainnet. Each section has CSV downloads.

Schedulers and clients

Schedulers

Vanilla
The stock scheduler of the Agave, Frankendancer or Firedancer client.
Jito
A modified version of the client with a built-in Maximum Extractable Value (MEV) auction and block engine, to increase revenue.
JitoBAM
A block-building extension for the Jito client that offloads transaction sequencing to external schedulers that run in trusted execution environments.
Rakurai
A performance-focused fork of Agave with its own scheduling and transaction processing.
Harmonic
An open block-building system. The validator runs Harmonic's client (Salsa, an Agave fork, or Samba, a Firedancer fork) and picks a scheduling strategy; a remote block builder that runs that strategy builds the blocks, and the validator streams them to the network. Harmonic tips are paid as priority fees.
Raiku
A sidecar that runs next to the validator client and sells guaranteed inclusion in upcoming blocks, booked ahead of time (AOT) or just in time (JIT).

Clients

Agave
The main Solana validator client, maintained by Anza. It continues the work of the Solana Labs client and is the reference implementation for the network.
Frankendancer
A hybrid client and the step towards full Firedancer. It combines the consensus and runtime of Agave with Firedancer's networking, signature verification and block packing.
Firedancer
A validator client written in C by Jump Crypto.

Harmonic strategies

FBA (Frequent Batch Auction)
Harmonic collects transactions in 50 ms batches and sorts each batch by priority fees and tips, highest first. Arrival time inside a batch does not matter.
FIFO (first in, first out)
Harmonic orders transactions by arrival. Fees and tips do not change the order.
MREV (maximum revenue)
Harmonic selects transactions continuously to capture the most revenue per block. The selection logic is proprietary.

Firedancer submodes

Revenue-optimized (BUN)
A Firedancer or Frankendancer submode that puts the most MEV and transaction revenue first.
Balanced (BAL)
A Firedancer or Frankendancer submode that trades off revenue and performance.
Performance-optimized (PRF)
A Firedancer or Frankendancer submode that puts network performance and low latency first.
Puffin mode (PUF)
A Firedancer submode named after the Puffin validator, whose Pebble scheduler holds non-vote transactions for batch auctions about every 50 ms, ranked mainly by priority fees.

Data from 2026-01-01 to 2026-11-07. The data updates each day. See the methodology for the definitions, sources and CSV downloads.