Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #2720
Committed on Canton
Participant commits update 122096852f…f48b18Imported to the execution layers
Importer applies block #2720 from GatewayHeadStep durations aren't available on this connection, so per-step and total timings are omitted rather than shown as a misleading 0ms. The lifecycle stages above did occur (the Canton↔EVM correlation is confirmed); only the sub-step wall-clock timing is unavailable — it requires a data source that reports distinct step timestamps rather than an atomic commit.
Total
—
Block → Canton commit
—
Step durations aren't available on this connection, so timings are shown as “—” rather than a misleading 0ms. The stages did occur (the Canton↔EVM correlation is confirmed) — only the sub-step wall-clock timing is unavailable, as the sequencer reports the steps as a single atomic commit.
0x02f879830e4a2582068a85188122883f85188122884782520894cde5a67c6d6ca7141f14043be3888be2abcabb2f880de0b6b3a764000080c080a06d6f3c61712c14876fbe4311f8d717b1bfc63f56fcfb602b9a256de4761f9e67a01e349c4f099aae92cb8defa6f8053678e737dffe45477a201824142b546020b6