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