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