Developer finds 93% of fully-signed Safe multisig transactions are permanently unexecutable

A developer building an automated executor for Safe multisig transactions ran a read-only detector against 1,299 Base mainnet Safes before writing any code, scanning blocks from Base's early history through block 50,776,046. The scan identified 366 fully-signed but unexecuted transactions, yet 339 of them turned out to be permanently dead — roughly 93% of the total. The root cause is that Safe executes nonces strictly in order, so if a different transaction consumes a given nonce, the original remains in the queue indefinitely with no indication it can never run. The naive one-line detector missed this entirely because it never compared queued nonces against the Safe's live on-chain nonce, a gap only exposed by an additional RPC call. This finding shifted the project's focus: instead of an execution engine, the core product became a structured refusal system that explains precisely why a transaction cannot or should not be submitted.