Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #175333
Committed on Canton
Participant commits update 1220c1c9ee…722a8fImported to the execution layers
Importer applies block #175333 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.
0xf8ab50843b9aca00827e9094c709afe8e62ce180b6f90ea69e9a9c9ad50e7cdd80b844a9059cbb00000000000000000000000024a09dd2a4aad57a02e3575a7b8d9d2cd447804700000000000000000000000000000000000000000000021e19e0c9bab2400000831c946da04b2b98376eeceff4661f6468047a5121524c427cd476bb019d96e4a5a305e409a04573941287f58f48a5ebd2dd2c0cff4f723ee90315a1a463f3687b834f08f5e4