Median production interval
1,000 ms
23 linked consecutive pairs
Finality monitor
Is the chain producing and finalizing blocks on time?
Source and guide ↗
flop finality --helpPublic observationCapture time below
Captured from hosted MCP ↗.
Poll and server cache: 15 seconds. Hidden tabs pause polling. A failed read pauses updates and keeps the last observation.
Indexed production and reported finality are separate observations. No consensus proof is checked.
Reported finality lag
4 blocks
Pinned rule result: normal
Latest indexed block
3,058,877
Not the finalized prefix
01 / Block production
Follow the parent links.
New observed hashes enter from the right. Each bar is the interval from its linked parent, scaled to this window's maximum. Select a block to inspect it.
Select a block for its full hash, parent and timestamp. The strip shows the newest part of the measured window.
Full window: 3 intervals above 1000 ms. 0 excluded pairs. Missing heights, broken links and missing or non-increasing timestamps are excluded. Small timestamp differences are not a consensus verdict.
Latest indexed timestamp age at capture: 2836 ms. An old timestamp can reflect stale indexer data or stopped production. This sample does not distinguish them.
02 / Reported finality
Production is not finality.
The API reports best block 3058879 and finalized block 3058875. Their difference must match its reported lag.
0Warn > 30Freeze ≥ 120 blocks
Reported lag: 4 blocks. The gauge caps at the freeze boundary. Escape eligibility begins at 3600 blocks.
API state: normal. API safe mode: false. API thresholds match the pinned paper: true.
API thresholds: warn 30, freeze 120, maximum stall 3600 blocks.
No finalized hash, signature or storage proof is exposed by this query. Lag in blocks is not elapsed stall time. The paper specifies no finality latency target.
03 / Quoted boundaries
Know what the alert means.
Warn above 30 blocks
Finality lag above which the detector reports Lagging (alert only; finality-clocked deadlines pause naturally).Pinned Appendix A rule ↗
Freeze at 120 blocks
Finality lag at/above which the channel enters Stalled: new finality-dependent opens are rejected fail-closed (ensure_finality_open_allowed); additive top-up/cancel paths stay open.Pinned Appendix A rule ↗
Escape eligible at 3600 blocks
Finality lag at/above which the chain is EscapeEligible (safe mode): restore AlephBFT finality or ratify a checkpoint recovery through the hard-fork runbook. ~1h at 1s blocks.Pinned Appendix A rule ↗
The rail tracks reading progress. Alerts compare the reported lag with the pinned paper. They do not claim that a runtime action was executed.
04 / Validator visibility
The set is not exposed here.
Observable
Block hashes, parent links, timestamps and reported finality heads are exposed by the captured indexer schema.
Unavailable
Active validator membership, session keys, selected committee identities and rotation events. No count is inferred from miners or active operators.
Section 15 separates the authoring set from the selected finality committee. Registration enters ValidatorQueue. Rotation promotes into ActiveValidators using stake and performance gates with churn and minimum-set guards.
Read section 15 ↗05 / Recorder history
Keep the dates attached.
These are sampled indexed heights from the recorder. They are not a finalized-head series or a measurement of consecutive block times.
3,002,118
Indexed height
https://mcp.flop.network/mcp {"name":"flop_get_stats","arguments":{}}
3,040,412
Indexed height
https://mcp.flop.network/mcp {"name":"flop_get_stats","arguments":{}}
Showing the newest available recorder rows, capped at 12. Loaded from the public data branch.