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