Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #316391
Committed on Canton
Participant commits update 12203fe1fe…faa90bImported to the execution layers
Importer applies block #316391 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.
0xf8ac81928477d05ae482c140947b1d571c8eea785611a9a8f1faa5d70e0a96656380b844095ea7b30000000000000000000000002be095461f3bba2b53a34ba74f948f35b678c2170000000000000000000000000000000000000000000069e10de76676d0800000831c946ea0bc1d6478b5c5e90878662e16d2e21f0c4aa88d62bac391432b4c4ff85ebd0902a078bed84e6307d30f06ef5e5209a4c86132cbeeebf30a165b8e04447c4d8392cf