Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #16
Committed on Canton
Participant commits update 122000be31…38a52aImported to the execution layers
Importer applies block #16 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.
0x02f869830e4a2506010f825b11949cd46d9d3bb982e0450034e7349b5d54285f95c38435a4e90080c001a045a7b8d4d918ae5b4b93220f520da2c2ac1bf260168e868d3065b35810d1d8e6a01ff6559b237c4ea374f9b288dbc6552b3c0a21860b39c561ce3e9276c33aeadf