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