Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #116999
Committed on Canton
Participant commits update 122064d4bc…4d8eb5Imported to the execution layers
Importer applies block #116999 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.
0xf8aa0d8315f9098259a29411369e0a953fb0cd27db90d9ab532363ea6cd1e680b84440c10f19000000000000000000000000311f0fae5838d2fdfc76cb47c337084d3191eb4b00000000000000000000000000000000000000000000003635c9adc5dea00000831c946da032e165475bd90641ed8bf043429781986c41cff87c43b09bc336d52c67fdfc9ba021e54bacccae1b08d5f49d1ae665037045b3d491aed2d873c9db5e7b6bc302e0