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