Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #16833
Committed on Canton
Participant commits update 12200876cb…3b6fb4Imported to the execution layers
Importer applies block #16833 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.
0xf8ac80858bb2c970088259a294a0809c6182efe54bed9243c93944d1041615b8f280b84440c10f19000000000000000000000000b89da667f647b6edff37baea49a675ef5717f63000000000000000000000000000000000000000000000003635c9adc5dea00000831c946ea0bde603731793d6db9a1cb8cce70baaa36b9386369bda4053dcaa7cc5d734b012a02f8473a7cb4e5a517095ebe379f6dcab31e81772c38c19825cf7057f3618dffd