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