<p>Double spending is not possible because there are many miners checking the data independently and then verifying the result against each other.  The first 'spend' that gets put into the blockchain and verified is the only one that can count - if another one comes along, it is ignored.</p>

<p>A simple, and elegant, way to keep double spending impossible.</p>

CC BY-SA 3.0
2018-01-20T14:06:15.447Z
I'm talking about double the same transaction.
Tailer
CC BY-SA 3.0
2018-01-20T14:16:16.433Z
I am, too.  I used the same term you used in the question (and your tag), so I'm a bit confused by your comment.  Can you ask your question in a different way, or help me understand what you are looking for?  Perhaps various other posts (under the 'Related' section on the right) will help - I found https://bitcoin.stackexchange.com/questions/50375/understanding-a-bitcoin-double-spending-transaction-by-performing-one-on-yoursel?rq=1 explains how you CAN do it, though the end result is the same as my answer - only one transaction actually has a high enough count to verify it is valid.
Apps-n-Add-Ons
CC BY-SA 3.0
2018-01-20T13:24:55.337Z
2018-01-20T13:24:55.337Z
Apps-n-Add-Ons
<p>How it's possible to double spend a transaction if the transaction outputs are already spent? and why these types of attacks are not preventable? </p>

<p>is it about blockchain sync time between nodes?</p>

<doublespend>
how to double spend Bitcoin transaction?
Tailer
# how to double spend Bitcoin transaction?

(Asked by: username_0 on 2018-01-20)

How it's possible to double spend a transaction if the transaction outputs are already spent? and why these types of attacks are not preventable?

is it about blockchain sync time between nodes?

**Tags:** doublespend


---

## 1 answers

### Answer by username_1 on 2018-01-20. Score: 0 | Accepted answer

Double spending is not possible because there are many miners checking the data independently and then verifying the result against each other. The first 'spend' that gets put into the blockchain and verified is the only one that can count - if another one comes along, it is ignored.

A simple, and elegant, way to keep double spending impossible.

> **Comments:**
> **username_0**: I'm talking about double the same transaction.  
> **username_1**: I am, too.  I used the same term you used in the question (and your tag), so I'm a bit confused by your comment.  Can you ask your question in a different way, or help me understand what you are looking for?  Perhaps various other posts (under the 'Related' section on the right) will help - I found https://bitcoin.stackexchange.com/questions/50375/understanding-a-bitcoin-double-spending-transaction-by-performing-one-on-yoursel?rq=1 explains how you CAN do it, though the end result is the same as my answer - only one transaction actually has a high enough count to verify it is valid.  

---

