Full lifecycle view
Gateway_FinalizeBlock
Block timestamp → commit, incl. the gateway-build-block call for block #276359
Committed on Canton
Participant commits update 12202308e9…f8dfc5Imported to the execution layers
Importer applies block #276359 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.
0xf8ac24850632dfd4d88259a2940db987998cdceb19be8b3dd513f173fb1c32fe8980b84440c10f19000000000000000000000000209093888bbbcc7e800bb82fddc3dddfc8e82f5d00000000000000000000000000000000000000000000003635c9adc5dea00000831c946ea035a5d246ff93641d0d2be4dddcbb6ba1d372e034a32a0d32d9c2005f6bfbdf09a00880192339b7be2d3093569c4ccec61c741795722027b341a96748113138c951