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