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