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