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