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