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