Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #296855
Committed on Canton
Participant commits update 1220f7e9db…1cef1bImported to the execution layers
Importer applies block #296855 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.
0x02f8f5830e4a2582026c8459682f008459682f0e8301355094e57aea293f0e88806be9542b05e18e8efb85ee3880b884d16a4010000000000000000000000000ba00a80e6d83fce7244b144ac78a1fb00de22db5000000000000000000000000d22691c2154f8b4c343c2960fa6152062f10a7f9000000000000000000000000000000000000000000000000a688906bd8b00000000000000000000000000000000000000000000000000000a688906bd8b00000c001a0adaa3c8e9b8b1bae3064ec67c2f8d6dac123503332e8e6a618470813c81181a8a06ec38eaf1f3eeb879909bb041956443618fec06429cb84d95e9c33bb0d0832fc