Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #222200
Committed on Canton
Participant commits update 122092a926…aaf97dImported to the execution layers
Importer applies block #222200 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.
0xf8ac10850e6a90001f8259a294e0a45ef66d2db5e766eba1f70e21a4bf1f901b8780b84440c10f190000000000000000000000004c4985301e5f82d8cec6ff5eb49d865420c7113a00000000000000000000000000000000000000000000003635c9adc5dea00000831c946ea035f2fac42647f0e23427fe32fc087d501053087af253cf968fee593ff7ba5a45a03d71db8f5aa81aad9568f20aa61048a6a5b5f7fac3d642f312e995f2450e6fa5