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