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