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