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