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