Real Flow mainnet data
Home/chains/flow-mainnet
Chain overview

flow-mainnet

Head
168391034
Finalized
168391034
Blocks
1
Transactions
2
The pipeline is behind the chain tipflow-mainnet

Everything already published is complete and correct; only newer blocks are missing. The chain summary reports this generation as behind the tip.

How far back this chain can be debugged

Stepping a transaction means re-executing it, and that needs the state the chain was in just before it ran. On this chain it is obtainable at block 137390146 and above, and not below. THAT IS A LIMIT ON WHAT CAN BE RECORDED, not on what is published here. A transaction already recorded carries its own execution and steps from it for good; the boundary says that a transaction below it cannot be recorded NOW, because the state a replay would have to start from is not reachable by the pipeline that records this chain. The sentence below is that pipeline's own record of what it measured.

Of the 2 transactions recorded here, 2 step at source level, which needs verified source and debug information for every contract a transaction ran, and none steps one VM instruction at a time. A debug tier belongs to each recording rather than to the chain, so this counts what was recorded and promises nothing about the next transaction.

How that boundary was established, in the pipeline's own words: “the access node this capture read (access.mainnet.nodes.onflow.org:9000) serves state only from its own spork's root, block 137390146, and refuses the block below it. That is the node's retention, an operational limit: earlier sporks are served only by their own nodes, so it is not where the chain's history begins”

Recordings on this chain are executed from the cadence-ast format. Each transaction's page states the granularity its steps are reported at: source lines where the contract's source was resolved, otherwise the format's own units.

How each trace on this chain is checked, in the pipeline's own words: “each transaction is re-executed by the network's own FVM and compared with what the chain recorded (status, every event with its values, and the computation), and one that does not match is published as divergent, never as a trace of the chain. Its Cadence source is the contract code the execution read from chain state, so no third party supplies it, and a file that does not hash to that code is discarded”

Latest blocks

HeightBlock hashTxsFinalityParent
1683910340x95f8…1ca72Finalized0x8ec7…fa96

All blocks →

Latest transactions

DebugTx hashBlockFromTo / targetMethodFeeStatus
DebugSources available0xc8f9…0611168391034:00x18eb…26d2——374 / 9999 computation · 0.01506000 FLOW · 0.00000374 effort · 1.00000000 effortSucceeded
DebugSources available0x73cd…04c4168391034:10x2093…bd80——0 / 9999 computation · 0.00000000 FLOW · 0.00000000 effort · 1.00000000 effortReverted

All transactions →

About this data

Real Flow mainnet data — Blocks and transactions taken from the live network. This is a preliminary export covering 20 October 2026.