Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #5040
Committed on Canton
Participant commits update 12205c6c94…d060acImported to the execution layers
Importer applies block #5040 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.
0xf86d808519bacaa8af8261a8945ec679d28c47226c549891cf83fd3c463432143c865af3107a400080831c946da011f87fbff25afa758f15a7173f8ae9a8c0ece296be58ef4ca4df293f7f5fd0faa01819bcad201553493daa8df6c91daaca3bcd85c0921aa0280421a19f3f45cc4d