Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #160650
Committed on Canton
Participant commits update 122076d2c6…e391abImported to the execution layers
Importer applies block #160650 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.
0xf8ac0f858bb2c970088259a2945345a589ea2a5896673ff13987bcda49d3569be780b84440c10f19000000000000000000000000aaace973ef3e3fcdb64b8888a77775dd6692d31f00000000000000000000000000000000000000000000003635c9adc5dea00000831c946ea04aea28f1c435721e1801700ec42764bafd48f73730005434efbc34a2bca5a181a00cdc2170a6d2752c39bc17f07db7d79dfc65f3c44bef9e6421429f4a4cf015ef