Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #123471
Committed on Canton
Participant commits update 1220000008…8a3b3cImported to the execution layers
Importer applies block #123471 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.
0xf86c0c8407270e0082520894cd19907545ed200ab4aa8043af4b18bb1ec66bda865af3107a400080831c946da038bd1a047d5ba3ea681f7aba57e324ed825716f2ebc30e772d8a35b136b447fca05ec16bb25df1f4d597bac585feb8c1cacb496f17513b020671fd995a61534dbd