Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #242375
Committed on Canton
Participant commits update 122084f3ee…9d7ac8Imported to the execution layers
Importer applies block #242375 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.
0xf88b11850c0378001a8254ac94a2766fc6dabb3f3e56a9a4bf49f59dbc2e7b16d280a4552410770000000000000000000000000000000000000000000000000000000000000001831c946ea06104ab5f8829a5d4457fe301875eefd7ce1e0bf868ffdc6366e9108800817481a03ba15b60d063a07d87de93516a2eb3b796705a2f2683f6cdfca2ef69ad387b87