Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #32017
Committed on Canton
Participant commits update 1220032bdd…d9cbf6Imported to the execution layers
Importer applies block #32017 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.
0xf8ac03858bb2c970088259a29451be323af717fdc9555254a39fe99a0cbce167ed80b84440c10f19000000000000000000000000262e515007541d6ec0f32ebf35b7eee22ca2389c00000000000000000000000000000000000000000000003635c9adc5dea00000831c946ea08764fe8686af049ae8e63cba5d67643d7561e400fd77cc4bf62e376290470361a05db31519106694f29704d8628e8a138faf939545b25cc673e18dfc40fe9aa704