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