Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #19220
Committed on Canton
Participant commits update 122069de4e…6f2ca9Imported to the execution layers
Importer applies block #19220 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.
0xf8ac80853744bb1e0f8259a2940db987998cdceb19be8b3dd513f173fb1c32fe8980b84440c10f19000000000000000000000000153e74d6cd699bc198cc64330143fe1e8c2f55a600000000000000000000000000000000000000000000003635c9adc5dea00000831c946ea00781931459dbb5ec30f995575ab5de54c0ab92bd7df3ff2b1ed61524e43930eea0254db201bd8fed5d7b71a5d39192ee1e7058e537c7c43aa16e30a8ccc9b0fd05