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