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