Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #262025
Committed on Canton
Participant commits update 122057381c…cc4beeImported to the execution layers
Importer applies block #262025 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.
0x02f891830e4a2501843b9aca0e843b9aca0e826f009495447ef5db517a03a1d90594bdbe3dbdc9c9ce4780a41003e2d2000000000000000000000000000000000000000000000000000000000000004ec001a01b869034141fa257caddb7a543068ea858df51fe9231df93359c24a88d46632ea068ab9098eda06c5c25d990afd9e7000e67e2152176c3861c27258e6531b86fdb