Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #83296
Committed on Canton
Participant commits update 122037d4de…d3e9cbImported to the execution layers
Importer applies block #83296 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.
0xf8ac06858bb2c970088259a29423e5dee888c67549a750290c1ba14a94c855229a80b84440c10f19000000000000000000000000108350551e267e6043f0761f984c98463bb5be3d00000000000000000000000000000000000000000000003635c9adc5dea00000831c946da04a7effe2cbeaf098176cfab8e6363dcd09ecfb32db04730f4c8869605a19393ca06722082af8f209fa119d669346824122d08170fbb271ad90a01c6d383ff3c104