Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #45632
Committed on Canton
Participant commits update 122036412f…9be7f3Imported to the execution layers
Importer applies block #45632 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.
0xf88b01858bb2c970088254ac947919e636cc2a6edbbb60c3d696509f90f5505a5b80a4552410770000000000000000000000000000000000000000000000000000000000000001831c946ea05e0ed5620ce2bcfa911002d08839968fce3c325071b223ead22f569b3976c057a03f866d4f71be197c1e639026af1030be02e0869ec917dad15e02f0af4cf70950