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