An inefficient algorithmic complexity issue exists in the `remaining transaction value` function. During contextual verification, the software clones the entire block-level spent-UTXO (Unspent Transaction Output) map for every transaction. An attacker can exploit this by mining or seeding the mempool with approximately 26,000 minimal single-input transactions within a single block, which can stall every validating node for more than 52 seconds.