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