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