Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #184590
Committed on Canton
Participant commits update 122037e75e…dbd4f3Imported to the execution layers
Importer applies block #184590 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.
0x02f8b3830e4a2507843b9aca0e843b9aca0e8301668194fddb72f8b030e6fff758378f8bcb6aa2a2f6ae5180b84440c10f1900000000000000000000000089966e6b66187fccb198d851e0d433a43dbcfda70000000000000000000000000000000000000000000000000000000089966e6bc080a09a20ca6770382dd0f8fa3a87936147e20e1771f1c8e5bcfc5962e353cd7a935ca0173984a77283396f0ebd83b2797230707c273967910f4e11448a5da486645b1c