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