schedulers.watch

Solana validator block revenue by scheduler

Revenue shows what the blocks of each leader earn: base fees after the burn, priority fees, Jito tips, Rakurai TIN and other tips. Every channel is net: the part that the validator receives.

The charts show revenue per block, the spread of revenue across blocks, the share of each channel, and revenue per second of slot time. Revenue per second keeps a longer slot from looking like more revenue.

Revenue is what the blocks earn, not what the validator keeps after its commission to stakers. USD values use the average SOL price of each day.

Solana Observer shows what each block paid in full: all base fees, all priority fees, and tips before the Jito and Rakurai commissions. Its revenue numbers are higher on purpose.

Revenue: terms

Block revenue

The value a leader realizes from its blocks.

base fees after the burn + priority fees + Jito tips + Rakurai TIN + other tips

Base fees count at the validator's half: the other half is burned. It is what the blocks earn, not what the validator keeps after its commission to stakers.

Revenue channels

The parts we split revenue into.

base fees · priority fees · Jito tips · Rakurai TIN · other tips

Every channel is net: the part the validator receives. Base fees are the validator's half (the other half is burned). Jito tips are 94 % of each tip, because Jito keeps 6 %. Rakurai TIN is 80 % of the Rakurai income of the block, because Rakurai keeps 20 % (see below). Other tips are the full tips to the other tip accounts we track. Priority fees do not include Rakurai payout transactions.

Rakurai TIN

The validator's part of all Rakurai income: tips, backrun share and subscriptions.

80 % × Rakurai tips when the block lands, for each block; + 80 % × (backrun share + subscriptions of each epoch) × the part of the epoch in the period, for each period

Rakurai TIN is net: the part the validator receives, like Jito tips. Rakurai keeps 20 % of each tip, backrun share and subscription (Rakurai's on-chain configuration, read on 2026-10-13), so we count 80 %. We count the Rakurai tips of each block when the block lands. Rakurai's on-chain ledgers give the backrun share and the subscriptions of each validator for each epoch. These two amounts are not paid in a block, so no block holds them. We divide the amount of each epoch over its UTC days by the part of the epoch's time in each day. The totals and the means of a period (the composition, the history, the weeks and the Validators table) add the days of the period. The distributions of single blocks and revenue per second show only the Rakurai tips that a block holds. Rakurai claims these amounts for the validator, usually in the next epoch. Then the validator pays its part to itself as the priority fee of a payout transaction in its own next block. We remove these payouts from priority fees, because Rakurai TIN already counts the same money. From 2026-10-13, a daily query finds the payout transactions. Before that date, we take each payout from Rakurai's claim transaction on Solana: the amount is exact. We put it in the validator's first block after the claim, or in a later block when the payout is larger than the fees of that first block. On a day without payout data, priority fees keep these payouts, and the coverage note says so.

Revenue per second

What a block earns for each second of slot time, so longer slots do not look like more revenue.

block revenue / leader's mean slot duration that day (s)

The slot duration is the leader's mean Ghost slot duration on the day of the block: first shred of a slot to the first shred of the next slot. A block has no value per second when its leader has no Ghost slot duration that day, so the history starts on 2026-02-11. The directory shows the mean over the leader's blocks.

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