Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #16
Committed on Canton
Participant commits update 122000be31…38a52aImported to the execution layers
Importer applies block #16 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.
0x02f90130830e4a250f8085e8d4a5100083015f909400000000000000000000000000000000000a7e0080b8c4068f173800000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000035a4e900000000000000000000000000000000000000000000000000000000000000005777322d626f622d313739333531373236353a3a3132323062363461656561386162653230373238613666363064363664366135373231326361396261326638643362376134356266386464346465363933326565666632000000000000000000c001a09ff4ee850474192aac94a4a2e39abed84f16440f369b5a412245c2228e8f8b1ba06ea91dcab040613e7fa72c081d96654f75bb044c5d572ea04a68cbd5120fc904