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