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