Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #2275
Committed on Canton
Participant commits update 1220543e2e…042b9fImported to the execution layers
Importer applies block #2275 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.
0x02f894830e4a2501851d67c309e6851d67c309ef8301076194d3bf8d58683f88356ba05249b143954eb63773a580a43fb5c1cb0000000000000000000000000000000000000000000000000000000000000005c001a01cc24927f83269c4dc12f1e6f0e99660ef74aa78c89dac08a7e663e845e4771ba02f65a9331f2cd71afadc77f62e8825514ce3f4bd75b01e574728a5bea4f062fa