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