Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #61999
Committed on Canton
Participant commits update 1220440dae…0300abImported to the execution layers
Importer applies block #61999 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.
0xf8ac06858bb2c970088259a2945345a589ea2a5896673ff13987bcda49d3569be780b84440c10f190000000000000000000000008eea6680f5f8f377f5b4e34f6d8786b6e96b4de800000000000000000000000000000000000000000000003635c9adc5dea00000831c946ea011d51040874265c724763f18409e962a0883449e6c51ea409692fac375607c3fa03a0576c85a4316474b09fb29e27aefd9782086e1edfe6d971b93c5c5f77594a3