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