Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #286150
Committed on Canton
Participant commits update 12200c2fce…ace98eImported to the execution layers
Importer applies block #286150 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.
0xf86d0b856b1d30355482520894fd7c5c8feda660b336cea19f9f429bf2c7084601865af3107a400080831c946ea0770af8b46505f3f2d5f0d69852c7f97991b2955951d657d180ca044a9b0fe00ba009e262237ecbdd309973d2c1af0b92dddea887852a0b9d9e0e44c74040db9e4a