Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #26905
Committed on Canton
Participant commits update 122030212a…8e0a47Imported to the execution layers
Importer applies block #26905 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.
0x02f8f5830e4a252185037e11d60085037e11d600830135bd94e57aea293f0e88806be9542b05e18e8efb85ee3880b884d16a40100000000000000000000000004bf1e7a0cf3139d0fe3ae712f1db210ad1f268b8000000000000000000000000c81e4c0b6c63be04d1eac2e56c648647901c24950000000000000000000000000000000000000000000000008ac7230489e800000000000000000000000000000000000000000000000000008ac7230489e80000c001a0bd197f22b5d5fe10eb5000f45c7fb81b4d09e7657f6863fe88cb2f1ef0550460a0417f413d2919df84dbc7fa033aed32a3f38e5224234d93b13ac51d8a35ff80f2