Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #121137
Committed on Canton
Participant commits update 122031e19c…862ba9Imported to the execution layers
Importer applies block #121137 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.
0x02f901f4830e4a258211b8830f4240831e8480830c98ce94925e8d5ec0b8c417bcadbeae4d7e7f22376003fc80b90184de11ad05000000000000000000000000a2863f93ea4890cb5eb6e7cde5ef25c93b5009a200000000000000000000000041f21e381a70e404854d1f95788208bbc6a8cd7200000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000009151d9c0c0000000000000000000000000000000000000000000000000000000004000c170000000000000000000000000000000000000000000000000000000000000014000000000000000000000000214a0c5ed66aa4b8ae836500b688518fcc03f50f000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c001a0f20fe1aefc282a0dcfb189ee9aa7c1836617336904220c7b310ae0883bc1c059a05ea00d27a803e656c1c8d844b289786fb67318b764d5f34c94b0141f7cdc6fd0