Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #1124
Committed on Canton
Participant commits update 12209fafda…d7d6f4Imported to the execution layers
Importer applies block #1124 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.
0x02f879830e4a25820213850210b75836850210b7583e82520894bb89e912d75923987e0426f0067680c26f828934880de0b6b3a764000080c001a0fb820e06cb42bf5ae2c8ac9f448b54a3aecaf73230c1758fcfc619fe03eb34f3a022f3ea91237116e8618870bfaef963872a059e6d3715c07e4f77d34171005d14