Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #108666
Committed on Canton
Participant commits update 1220591878…1df5c1Imported to the execution layers
Importer applies block #108666 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.
0x02f901f4830e4a258204a4830f4240831e8480830cbe6094925e8d5ec0b8c417bcadbeae4d7e7f22376003fc80b90184de11ad05000000000000000000000000a87685dc3f504463f049f6d8deed800ca6f8806800000000000000000000000041f21e381a70e404854d1f95788208bbc6a8cd720000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000194b663e3000000000000000000000000000000000000000000000000852a1bc8f2c18e3b0000000000000000000000000000000000000000000000000000000000000014000000000000000000000000924e07135a82f034b12537d45845ea554fdbd2e1000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c080a0f23ec6b21c13d4104a68ba3c195d15789ce21e22e08b662b498d53e5198d4de9a038550db53a752d7cea0b1341a2f53126c8db8e4ac012094e8b998616ff2f8e43