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