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