Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #242256
Committed on Canton
Participant commits update 12203228f7…c88ba1Imported to the execution layers
Importer applies block #242256 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.
0x02f8b4830e4a25598523df4cec868523df4cec9482cedd9484d3ba0083ab4f5f538f12e3be2a232ebb379b8f80b844a9059cbb0000000000000000000000008fc1a0713ac6499888bccb54b6a97cae17c8d21800000000000000000000000000000000000000000000000edba6ded9f09d0000c001a058e0935430b4867683d14c602290db51c2974a90cc6233e240213c7560ed8a41a02f9b4b4351c43ee36b88e9bbd09c42969a829b720aa0ab7083bf505a867a9460