Hold tight, the first sample is on its way.
Taking a reading…
The next 24 hours, one block of sky at a time.
Each hour shows the fee level it usually runs at, with a weather symbol relative to a normal hour. The chart underneath draws the typical value as a line and shades the middle half of past readings, so you can see how settled each hour tends to be.
Drawing the hourly strip…
Plotting…
Seven days at a glance.
For each weekday in your chosen time zone: the overall conditions, the calmest hour (low) and the most crowded hour (high), measured in priority lamports paid by a typical non-vote transaction.
Loading…
Every hour of the week, colour-coded.
168 squares, one per hour. Cool cyan means calm, orange means crowded. The small number is how many sampled blocks sit behind each square; striped squares have no reading yet. Hover or tap for the detail.
What sending costs at this moment.
Taken from the newest block we read plus the node's recent per-account fee floors. Dollar values use the live SOL price from Jupiter.
Waiting for readings…
| Checking in with each program… |
Weather stations: getRecentPrioritizationFees reports, for each of roughly the last 150 slots, the smallest priority fee (micro-lamports per compute unit) any transaction touching that program paid. Lots of zeros means a tip-free transaction would likely have landed; the upper columns show how hard people were competing.
No crystal ball. Just a lot of blocks.
Reading a block
A finalized block comes in through getBlock. Vote transactions are thrown out. For everything else, the tip is fee − 5,000 × signatures lamports, since 5,000 lamports per signature is the flat base charge. Each block keeps its median, 75th and 90th percentile, plus the share of transactions that tipped at all.
Live feed and catch-up
A fresh block every 2 minutes. Quietly in the background, one older block roughly every 12 seconds walks back across the past 7 days, aiming for one block per half-hour. Slot-to-clock conversion starts from getRecentPerformanceSamples and is corrected by every block's real blockTime; slots today run near 0.27 s rather than the textbook 0.4 s.
Sorting into hours
Readings land in 168 UTC hour-of-week slots (up to 8 weeks back, at most 96 blocks each). A slot's value is the median of its blocks; the shaded band is their 25th to 75th percentile.
When data is thin
An hour uses its own hour-of-week slot once it holds 3 or more blocks. Short of that, it borrows the same UTC clock hour from every day, and failing that, all readings together. The hourly chart colours each point by which one it used.
Blind spots
Jito tips travel as separate transfers and never appear in fee. A single block is a narrow window on a busy minute, and fresh squares rest on few blocks. Everything here describes what already happened on chain; the next hour is free to behave differently.