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