Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #219360
Committed on Canton
Participant commits update 12208a80cb…26050fImported to the execution layers
Importer applies block #219360 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.
0xf8ab7684872eef00827e90941bc0c072bbc7e9b953dcae5bac21c82ceec8df6280b844a9059cbb0000000000000000000000007011760a0f0bb2fc15fad422312289ec971b1ef400000000000000000000000000000000000000000000021e19e0c9bab2400000831c946da0cc92d7a0bc8ec0bd858f7de25cec7c8da5ceefa8726581c6a8cc5060b04bc7dca0129ce9d5684063b516c7dd0394ec76f0f77f2f7b32b28ea8c62736b502f3705f