Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #296748
Committed on Canton
Participant commits update 122067e7de…0c256eImported to the execution layers
Importer applies block #296748 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.
0x02f8f7830e4a2582016085037e11d60085037e11d600830176be94e57aea293f0e88806be9542b05e18e8efb85ee3880b884d16a40100000000000000000000000007e83a33f6c3482cc1c51eb24990a1fc2c9ddbf62000000000000000000000000a9f0c3fbf635b4432beeb65ad297f9a1dace81870000000000000000000000000000000000000000000000001bc16d674ec800000000000000000000000000000000000000000000000000001bc16d674ec80000c001a0a845cdaeb44a87625c451e1aa982672483a8b75cf82e958f7337436db4a7d96da024d0f44ccbb1a00ff575ff4ad03f7f9f0db6737b5deff033cf16183c8b7863f7