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