Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #185300
Committed on Canton
Participant commits update 1220386edf…4eab2cImported to the execution layers
Importer applies block #185300 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.
0x02f8d2830e4a2508843b9aca0e843b9aca0e82e07f946962b168b0f541ae9a632997e2bb7881c450c74e80b86423b872dd00000000000000000000000037105fe2dc874703e9d39148e0b6103fb2a1ecda000000000000000000000000bff2152c44bececbe607f64e51b5194c65f10def0000000000000000000000000000000000000000000000000000000037105fe2c080a031ffa2cbf20947efc3001587501772a7695720353fbac739683cdc629d0f684da05b1e73413cd693e5a87c8e892dcb5b793bd1c2d5800d25e66f1358d482d84365