Sui skips consensus entirely for transactions that only one person can touch Most chains put every transaction through the same pipeline: validators agree on a global order first, then execute. @SuiNetwork stores everything as objects, each owned by a single address, shared, or immutable, and that label decides the route. A transaction touching only your own objects has nothing to race against, so it skips the ordering step entirely, which Sui's docs say is why those transactions finalize with lower latency and sui:native gas. Shared objects, like a DEX pool anyone can trade against, still go through consensus, and a heavily used one becomes a queue. Sui's guidance runs accordingly: single-writer, latency-sensitive designs lean on owned objects, while anything multi-party pays the sequencing cost.