Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #263200
Committed on Canton
Participant commits update 12203b4de3…9d1fb5Imported to the execution layers
Importer applies block #263200 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.
0xf8ac1085027dbaad588259a294b778d58e24c877095693fc7800b3ee5834773d8080b84440c10f190000000000000000000000002b1bf3d0ee2aa15a7e211a60e048ff2e9d27845500000000000000000000000000000000000000000000003635c9adc5dea00000831c946da04d2e75f37a5a01f1747d43ee9a0815c141394613667d4c485eb9ec18f64dbaf8a011271363f27ce574dab4da9f928da520e039361fc42664e559c4afba279bd82f