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