Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #178005
Committed on Canton
Participant commits update 1220ec09e9…95c930Imported to the execution layers
Importer applies block #178005 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.
0x02f901f4830e4a25820fe4830f4240831e84808307339294925e8d5ec0b8c417bcadbeae4d7e7f22376003fc80b90184de11ad05000000000000000000000000a87685dc3f504463f049f6d8deed800ca6f8806800000000000000000000000041f21e381a70e404854d1f95788208bbc6a8cd72000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000018c6e3bda00000000000000000000000000000000000000000000000381ac4b6efce545880000000000000000000000000000000000000000000000000000000000000004000000000000000000000000e0f6d3e2e0dedbf8a37917a2e8aa6343bb395090000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c080a0ae124c0b8ebd1ddfb0ee77799e0835859c76a4edc71caf6efe317b8bfd5d1c0fa02683b6d6d3d13384924c2bcd4a0d898d2344bb1b59c4366cf13139802d4d2f65