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