Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #250200
Committed on Canton
Participant commits update 12209ac714…d1acc0Imported to the execution layers
Importer applies block #250200 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.
0xf88c818b8459682f00830178c194b7117275152a61088f68ed2618009891895a6e8b80a46a627842000000000000000000000000d38a608c0a511be6d426d3843aa2a8122e264097831c946da0c39feab43303a5a04ad34acac5add8c90009375bb9d65fa9fc3a52e241881db2a063d2cc1c1f120ca0b9e43292123e476b5df52fcc8b03e80796341b58ab49328a