Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #116296
Committed on Canton
Participant commits update 122083db5c…d7665aImported to the execution layers
Importer applies block #116296 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.
0x02f901f4830e4a25820e87830f4240831e8480830cba5994925e8d5ec0b8c417bcadbeae4d7e7f22376003fc80b90184de11ad05000000000000000000000000a2863f93ea4890cb5eb6e7cde5ef25c93b5009a200000000000000000000000041f21e381a70e404854d1f95788208bbc6a8cd72000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000081118de2a000000000000000000000000000000000000000000000000036e6312ccc3f0100000000000000000000000000000000000000000000000000000000000000014000000000000000000000000924e07135a82f034b12537d45845ea554fdbd2e1000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c080a02abf63b0285a928c2150363fb11b3f2ba4e0d24437e926bd9824973bdb2de45fa06c88627f12be2064ea56386dbed67936b46d77f9bc960979e4f033ef7ae3daf0