Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #262022
Committed on Canton
Participant commits update 12202cc3ef…1a94a6Imported to the execution layers
Importer applies block #262022 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.
0xf86c1e847b98a01a82520894235dc887c81c87cfa6d8a743aa93ace7c51b3c8c865af3107a400080831c946da0bab7aa5a5c6118776d6c7b98700d9d5ec816be9c1f52ef2328622d6dc717965ba06cf1b31a2e8018d6310a321853d975aba7bd2181d10a1d5c072b90cc60365825