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