Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #1896
Committed on Canton
Participant commits update 122052c4bb…5f22c9Imported to the execution layers
Importer applies block #1896 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.
0x02f879830e4a25820441850528f2b6e7850528f2b6ef825208947340cf9feda3e411105caf38ba475c66939f8c8b880de0b6b3a764000080c080a0298087b07e8134b5b23015c2579557a1f2f0952665534f3f0193d8bf542a902fa0087c9091617519a2846165f4069ee498fce1e15080e20a0d1029a71e5d1bcda6