Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #62503
Committed on Canton
Participant commits update 12207fa49c…d4baf2Imported to the execution layers
Importer applies block #62503 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.
0xf8ac03858bb2c970088259a2945345a589ea2a5896673ff13987bcda49d3569be780b84440c10f190000000000000000000000001b48ce356a7c3cabebaa395faad7e4b0a698c95300000000000000000000000000000000000000000000003635c9adc5dea00000831c946da09945b947a7818c1682fb5c1df2a1086fa40644f26a43991f5a38046bd2073f5aa06707d5bdf73d0e89b963f6e2e633dd89a843e2d9b1b9561719762e4efe79bf39