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