Unintentional double spend on blockchain after 3 normal transactions

[iluvbitcoins]

I have previously sent some low fee transactions that got into limbo, therefore I attempted this method
https://www.youtube.com/watch?v=ycq7O48aPvQ

With 1 1BTC input transfered to my Armory client, seemed successful
I have sent out these payments normally

https://blockchain.info/tx/073b5641509860ea55b60f50f745726ae18ec1b4599743f695b0722767805604
https://blockchain.info/tx/75a3553ab8143bd69bc37d8c7b245b24cf0beee6c9fa3acc70c40c8766b604c2
https://blockchain.info/tx/c4c237dd22b40f02927a89be6c617348216a65da51f4dcd0f65b81855f40c3c2

I just tried to send out some bitcoins and have gotten this

https://blockchain.info/tx/f5bc1cca6cf1b65b403a9f59d51d8bb9f97814d702dcca1d00a3ac83ea16dd27

After 3 successful transactions  

Should the transactions go through and confirm anyways?

[DannyHamilton]

You sent two transactions that BOTH spend the same output:

0.07678695 BTC output received by you on 2017-05-15 at 13:17:04 UTC at offset 1 in transaction c4c237dd22b40f02927a89be6c617348216a65da51f4dcd0f65b81855f40c3c2 using address 13uQEpboMnXWonGJkBW98bazQdx5M2Fnbe

You spent that 0.07678695 BTC output in BOTH:

983b00a7f3d8ea1fbbb0a5f3ae7d8faddb39a6b82c769ffe02d9c271f51428bb (sent 2017-05-15 at 14:28:04 UTC)
Sending:

• 0.0002 BTC to 15H9qevRm8KXLAeKQtyBURxD3rcEm8BuRU
• 0.04549667 BTC to 1Dmr9vpnMLmh8KUXyQWayJwHviLUhzx6Mi
• 0.0002 BTC to 1GPzKa26UeFywn6i7NMzEgrnKyvFuNt84h
• 0.0002 BTC to 1ND88YYgJ1sAhnCENHaZnoqVZimpZvhn2D
• 0.0001 BTC to 1CUiSECJL152seXbUgzrZci896iW89mPVy
• 0.0002 BTC to 1MuzKLFxWk3b1ApnBMgVdVKMPaLsFR6cxq

AND

f5bc1cca6cf1b65b403a9f59d51d8bb9f97814d702dcca1d00a3ac83ea16dd27 (sent 2017-05-16 16:34:40 UTC)
Sending:

• 0.015 BTC to 1FowGTphMGKoPd35pZ4m9anan8hJnPedrn
• 0.00014 BTC to 13NBQRX6vYZTNUTNtom39NRrjnizpqeZrF
• 0.00014 BTC to 13kJgyVh1g66hzLp3R9gwRzQebWj9mFdsS
• 0.03044667 BTC to 1C4Bs6VDgs9FqmySEU8ZPUufKfckFBRZus
• 0.00007 BTC to 1H4cDkUQGni4MSBMU7x1rCEK9nmLv1PgUL

Since an output can only be validly spent once in Bitcoin, only one of these two transactions can ever confirm.  Once one of them confirms, the other one will become invalid and will be abandoned by the network.

[iluvbitcoins]

How is this possible?

These are the only transactions that appear in my wallet


As the wallet stands I'm short for 0.016 which weren't sent anywhere o.o

[DannyHamilton]

On 2017-05-12 you received 0.1 BTC at address 1KUahjdCH99pNhLa2yF4hsuUdNxUKs3J5g in transaction 0c547c903e10859396bf4fa83610eff3b7a5fd137cf0098afddd2d3657da45e7.

On 2017-05-15 at 12:30:52 you spent that 0.1 BTC in transaction 75a3553ab8143bd69bc37d8c7b245b24cf0beee6c9fa3acc70c40c8766b604c2 to send 0.0163 BTC split across 112 different addresses.  After paying a transaction fee of 0.00691305 BTC, the remaining 0.07678695 were sent back to your wallet using a change address of 13uQEpboMnXWonGJkBW98bazQdx5M2Fnbe.  It confirmed 74 minutes later.

Then on 2017-05-15 at 13:17:04 you spent that 0.07678695 BTC in transaction c4c237dd22b40f02927a89be6c617348216a65da51f4dcd0f65b81855f40c3c2 to send 0.028 BTC split across two different addresses. After paying a transaction fee of 0.00199028 BTC, the remaining 0.04679667 BTC were sent back to your wallet using a change address of 17EYn87aWXxQd39UPpUBU3SFFNpmRsNzmK.  It confirmed 30 minutes later.

Then you spent that 0.04679667 BTC twice in the two transactions I mentioned earlier.

I don't know what you're doing with your wallet, so I don't know why it would allow you to spend the 0.04679667 BTC twice.

Did you recover a backup recently?  If you did, then the backup might not have had the 983b00a7f3d8ea1fbbb0a5f3ae7d8faddb39a6b82c769ffe02d9c271f51428bb in it?

Are you using the same wallet file in more than one copy of the software?  If you are, then one copy might not know about the transactions created by the other copy?

Are you creating raw transactions?  If you are, then you may have accidentally specified the same input in two different transactions?

[gangtraet]

Adding to the list above:

If you use an offline instance of Armory then it is easy to accidentally generate a double-spend.  Just make two transactions, then sign them both at the same time.  Only if you make a transaction, sign it and broadcast it before making the next can Armory avoid making a double spend.  This is because the online version of Armory cannot know if you are ever going to sign an unsigned transaction it made, or if you abandon it.  So it cannot block those coins from being spent again.

Of course, once you have created two transacations that double-spend the same amount, Armory and/or Bitcoin Core should normally prevent you from transmitting both of them.  But many things can go wrong that causes them to lose track of the first unconfirmed transaction, and allow the second to be transmitted.

[iluvbitcoins]

Okay

What the actual fuck

https://blockchain.info/tx/f5bc1cca6cf1b65b403a9f59d51d8bb9f97814d702dcca1d00a3ac83ea16dd27


What are you doing Armory 

[goatpig]

Chances are you were short on blocks.

[iluvbitcoins]

Chances are you were short on blocks.

Can you translate this to the common tongue? 

[achow101]

Chances are you were short on blocks.

Can you translate this to the common tongue? 

Your node or Armory's database did not have a fully synced blockchain.