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