Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #2050
Committed on Canton
Participant commits update 122041a98e…08af35Imported to the execution layers
Importer applies block #2050 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.
0x02f879830e4a258204a3851428ec710b851428ec7113825208944696efa249eff994282a999ac1b71bf7b39d35e1880de0b6b3a764000080c080a0253a8cf7734fe78d325f04fef06b12debc34b9ccac5353906851c8017b40c3e1a05e861df3ddbdb805821e57589faa60fbf62c7b27833c6233f770bb178eb2efc8