Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #161019
Committed on Canton
Participant commits update 122044f69a…0cfcc1Imported to the execution layers
Importer applies block #161019 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.
0xf8ac0f858bb2c970088259a2940db987998cdceb19be8b3dd513f173fb1c32fe8980b84440c10f19000000000000000000000000fb0b8c727f6c62e15e2edffa6a59d1b4e8ed060900000000000000000000000000000000000000000000003635c9adc5dea00000831c946da0e331361fcdef93a1cb3bc2c7aca0f07e0e3b4a9806f6a1f78db34ff3e868df13a030d006c395dc9776f8fdd4f8ded671a0c4059c49b8929ba8cb10b26e28064ae0