← GlossaryWallet basics
What Is a Double Spend? The Problem Blockchains Solve
A double spend is spending the same digital coins more than once; blockchains prevent it by agreeing on a single public order of transactions so a second spend of the same coins is rejected.
Key takeaways
- Digital files copy for free, so digital money needs a way to stop the same coin being spent twice.
- Blockchains solve this with a shared, ordered ledger that every node checks.
- Once a transaction is deep in the chain, reversing it would require redoing a lot of proof of work.
- Risk remains for unconfirmed payments and on chains with little hashing power.
The problem
If digital money were just a file, you could copy it and pay two people with the same coin. Traditional systems stop this by having a trusted party, such as a bank, keep the ledger and refuse the second payment. Bitcoin's original paper frames the difficulty exactly this way: the payee cannot verify that a previous owner did not already spend the coin elsewhere.
How a blockchain prevents it
A blockchain replaces the trusted party with a public, ordered ledger. Every transaction spends specific earlier outputs, and each node checks that those outputs have not already been spent in the history it follows. If two conflicting transactions spend the same coins, only one can be included in the chain, and nodes reject the other as invalid. Proof of work decides which history is the real one, by giving the most work the final say.
Where double-spend risk still exists
An unconfirmed transaction is only a promise: until it is in a block, a conflicting transaction could be mined instead. Even confirmed transactions can be reversed if an attacker controls enough hashing power to rebuild a longer chain, which is the 51% scenario. The deeper a transaction is buried, the more work an attacker would need to redo, so risk falls with confirmations.
What it means for you
When you receive a payment you cannot easily reverse, such as goods delivered or an exchange of coins, wait for enough confirmations for the amount at stake. When you send, there is nothing to worry about on your side: your wallet only spends outputs it controls, once.
Example
You receive 50 coins and the transaction shows as unconfirmed. The sender also broadcasts a conflicting transaction paying the same coins back to themselves with a higher fee. If a miner includes the conflicting one first, your payment becomes invalid. Waiting for a confirmation before handing over goods avoids this.
Put it into practice
Receive coins you control
Scrypt Wallet gives you a receive address for each coin, so you can wait for the confirmations that suit the amount before you rely on a payment.
Create a free wallet Get Scrypt for AndroidFrequently asked questions
Can a blockchain transaction be double spent?
Normally no once it is confirmed and buried, because nodes reject conflicting spends. Risk exists for unconfirmed payments and for attacks on chains with little hashing power.
Why do wallets show confirmations?
Each confirmation is another block built on top, which makes reversing the payment harder and double-spend risk smaller.
Is a double spend the same as a chargeback?
No. A chargeback is a bank reversing a card payment. A double spend is an attacker or error creating a conflicting payment on the same coins.
Written by the Scrypt Wallet team · Updated 2026-10-02. General education, not financial, tax or legal advice.