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