Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #111573
Committed on Canton
Participant commits update 12207bafb3…e758adImported to the execution layers
Importer applies block #111573 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.
0x02f901f4830e4a2582089c830f4240831e8480830c997794925e8d5ec0b8c417bcadbeae4d7e7f22376003fc80b90184de11ad05000000000000000000000000a87685dc3f504463f049f6d8deed800ca6f8806800000000000000000000000041f21e381a70e404854d1f95788208bbc6a8cd72000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000019b9771fb0000000000000000000000000000000000000000000000001e589c13c66bced50000000000000000000000000000000000000000000000000000000000000014000000000000000000000000214a0c5ed66aa4b8ae836500b688518fcc03f50f000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c001a0e9b03de9128ae19d0096ebed40cc2f3f702047e0c7d8d75714f60baa15442a4da00ed3c5c806bc9d7becb2e8f469d2189f2b7429c47ee1d97948afc7ac6765a0ed