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