Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #1822
Committed on Canton
Participant commits update 12201bbdbe…27204cImported to the execution layers
Importer applies block #1822 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.
0x02f879830e4a25820413850346b27c42850346b27c4a82520894bea6a752cf87674aad096827e656bf1efb50d006880de0b6b3a764000080c001a043295bfb3f2fdbeb225886ecafbbdf58521eab820c9a17af83dec477e9eba23aa03b479e1a577241bbacf6bceea785efca110802a57e2f73848a04e081746b2c98