Author

Topic: Another BTC Transaction.... Predicament? (Read 802 times)

full member
Activity: 210
Merit: 100
July 21, 2016, 11:46:20 PM
#12
I'm using Windows 10 Home x64. I'll wait for your guys' responses before I proceed with the commands. I'm guessing I should back everything up prior, which I'll do now.
Yes, you should always backup your wallet.

To start Bitcoin Core with -zapwallettxes, first shut down Bitcoin Core. Then right click the shortcut on your desktop and choose "Properties". In the box labeled "Target", click it and move the cursor all the way to the right so that it is past what is already in there. Then type -zapwallettxes. Make sure there is a space between what is already there and what you typed. Then click "OK". Then double click the shortcut and it will start Bitcoin Core with that option. When Bitcoin Core has started, you can remove that option by repeating what you just did but remove instead of type.

So after this command, the unconfirmed transactions will disappear from "Recent transactions" and the BTC will return to my wallet balance?
Yes. You will now be able to spend your Bitcoin as if those unconfirmed transactions had never happened.

Wow, you're amazing! The funds have been returned to my balance. Expect a tip heading your way!

Thanks so much for all of the help, knight!!

YOU ARE THE MAN!!
staff
Activity: 3374
Merit: 6530
Just writing some code
I'm using Windows 10 Home x64. I'll wait for your guys' responses before I proceed with the commands. I'm guessing I should back everything up prior, which I'll do now.
Yes, you should always backup your wallet.

To start Bitcoin Core with -zapwallettxes, first shut down Bitcoin Core. Then right click the shortcut on your desktop and choose "Properties". In the box labeled "Target", click it and move the cursor all the way to the right so that it is past what is already in there. Then type -zapwallettxes. Make sure there is a space between what is already there and what you typed. Then click "OK". Then double click the shortcut and it will start Bitcoin Core with that option. When Bitcoin Core has started, you can remove that option by repeating what you just did but remove instead of type.

So after this command, the unconfirmed transactions will disappear from "Recent transactions" and the BTC will return to my wallet balance?
Yes. You will now be able to spend your Bitcoin as if those unconfirmed transactions had never happened.
full member
Activity: 210
Merit: 100
You can rebroadcast the previous raw transaction (which I doubt you have) and when it confirm, the transaction you have made will also confirm. If not, you can only use -zapwallettxes to remove the transaction in question. Next, you have to ask the sender of the transaction you received from to send one more time.

Great, thanks for the advice. I actually did try to rebroadcast that first tx w/o the fee, but it failed. So I guess the -zapwallettxes is the way to go at this point.

The transaction you talked about in that thread is the same transaction which is blocking the transaction you are trying to send now. Do you still see that transaction (the one in the other thread) in your transaction list?Do you still need to send those Bitcoin?

I think the solution for you would be to start Bitcoin Core with the -zapwallettxes option. This will clear all of the unconfirmed transactions from your wallet. At that point you can then redo your transactions. It will be as if those two transactions had never happened in the first place.

Starting with -zapwallettxes is dependent on your os. What os do you use?

I'm using Windows 10 Home x64. I'll wait for your guys' responses before I proceed with the commands. I'm guessing I should back everything up prior, which I'll do now.

So after this command, the unconfirmed transactions will disappear from "Recent transactions" and the BTC will return to my wallet balance?
staff
Activity: 3374
Merit: 6530
Just writing some code
I sent a transaction on 7/14/16 without any tx fees (which was my fault, I admit). I actually opened a thread for that as well:

https://bitcointalksearch.org/topic/btc-mining-bounty-1552274

Since then, I have made some successful transactions that went through without any issues at all. It figures the biggest transaction I've ever sent would get stuck like this...

What to do?? I'm totally lost now.
The transaction you talked about in that thread is the same transaction which is blocking the transaction you are trying to send now. Do you still see that transaction (the one in the other thread) in your transaction list?Do you still need to send those Bitcoin?

I think the solution for you would be to start Bitcoin Core with the -zapwallettxes option. This will clear all of the unconfirmed transactions from your wallet. At that point you can then redo your transactions. It will be as if those two transactions had never happened in the first place.

Starting with -zapwallettxes is dependent on your os. What os do you use?
legendary
Activity: 2982
Merit: 4193
The problem is that it is spending from a transaction that doesn't seem to exist, d890605be31f55e0ce8e748b4b056bc7841aecf51bc95d5d3445799606f85df1. This transaction appears to have been dropped, and because of this, your transaction cannot confirm.

You will not lose any Bitcoin. If the transaction confirms, then it goes to the destination. If it is dropped from the network, then it will be as if that transaction had never existed in the first place.

Thanks knight. Do you know what would cause this even though I paid the recommended fee and "did everything correct," per se? At least, I hope I did.

I'm seriously thinking about switching to another wallet... but not exactly sure if it's the wallet's fault. It's all kind of confusing and not very user friendly.

Also, do you have any idea of a brief ETA on how long the transaction will either reach its destination or drop and be refunded? It'll be refunded right? I'm trying to figure out what "...then it will be as if that transaction had never existed in the first place" means.

Ugh, sorry for all of the questions. This is just frustrating.
It has nothing to do with the fee, although this should not have happened with Bitcoin Core. This is happening due to the way that Bitcoin works.

In order for a transaction to confirm, all of the transactions that it spends from must also be confirmed. What happened here is that one of the transactions you are spending from is unconfirmed, in fact, it has even dropped from the network. Because that transaction is not confirmed, your transaction cannot confirm either, regardless of the fee and priority.

The issue here is that your wallet let you spend from an unconfirmed transaction. This should not happen with Bitcoin Core. The only way that this could happen is if it were spending from the change output of that transaction. This means that one of your recent spends must have not confirmed. Double check your transaction history and see if you see any recent spending transactions that has a low fee.

I sent a transaction on 7/14/16 without any tx fees (which was my fault, I admit). I actually opened a thread for that as well:

https://bitcointalksearch.org/topic/btc-mining-bounty-1552274

Since then, I have made some successful transactions that went through without any issues at all. It figures the biggest transaction I've ever sent would get stuck like this...

What to do?? I'm totally lost now.
You can rebroadcast the previous raw transaction (which I doubt you have) and when it confirm, the transaction you have made will also confirm. If not, you can only use -zapwallettxes to remove the transaction in question. Next, you have to ask the sender of the transaction you received from to send one more time.
full member
Activity: 210
Merit: 100
The problem is that it is spending from a transaction that doesn't seem to exist, d890605be31f55e0ce8e748b4b056bc7841aecf51bc95d5d3445799606f85df1. This transaction appears to have been dropped, and because of this, your transaction cannot confirm.

You will not lose any Bitcoin. If the transaction confirms, then it goes to the destination. If it is dropped from the network, then it will be as if that transaction had never existed in the first place.

Thanks knight. Do you know what would cause this even though I paid the recommended fee and "did everything correct," per se? At least, I hope I did.

I'm seriously thinking about switching to another wallet... but not exactly sure if it's the wallet's fault. It's all kind of confusing and not very user friendly.

Also, do you have any idea of a brief ETA on how long the transaction will either reach its destination or drop and be refunded? It'll be refunded right? I'm trying to figure out what "...then it will be as if that transaction had never existed in the first place" means.

Ugh, sorry for all of the questions. This is just frustrating.
It has nothing to do with the fee, although this should not have happened with Bitcoin Core. This is happening due to the way that Bitcoin works.

In order for a transaction to confirm, all of the transactions that it spends from must also be confirmed. What happened here is that one of the transactions you are spending from is unconfirmed, in fact, it has even dropped from the network. Because that transaction is not confirmed, your transaction cannot confirm either, regardless of the fee and priority.

The issue here is that your wallet let you spend from an unconfirmed transaction. This should not happen with Bitcoin Core. The only way that this could happen is if it were spending from the change output of that transaction. This means that one of your recent spends must have not confirmed. Double check your transaction history and see if you see any recent spending transactions that has a low fee.

I sent a transaction on 7/14/16 without any tx fees (which was my fault, I admit). I actually opened a thread for that as well:

https://bitcointalksearch.org/topic/btc-mining-bounty-1552274

Since then, I have made some successful transactions that went through without any issues at all. It figures the biggest transaction I've ever sent would get stuck like this...

What to do?? I'm totally lost now.
staff
Activity: 3374
Merit: 6530
Just writing some code
The problem is that it is spending from a transaction that doesn't seem to exist, d890605be31f55e0ce8e748b4b056bc7841aecf51bc95d5d3445799606f85df1. This transaction appears to have been dropped, and because of this, your transaction cannot confirm.

You will not lose any Bitcoin. If the transaction confirms, then it goes to the destination. If it is dropped from the network, then it will be as if that transaction had never existed in the first place.

Thanks knight. Do you know what would cause this even though I paid the recommended fee and "did everything correct," per se? At least, I hope I did.

I'm seriously thinking about switching to another wallet... but not exactly sure if it's the wallet's fault. It's all kind of confusing and not very user friendly.

Also, do you have any idea of a brief ETA on how long the transaction will either reach its destination or drop and be refunded? It'll be refunded right? I'm trying to figure out what "...then it will be as if that transaction had never existed in the first place" means.

Ugh, sorry for all of the questions. This is just frustrating.
It has nothing to do with the fee, although this should not have happened with Bitcoin Core. This is happening due to the way that Bitcoin works.

In order for a transaction to confirm, all of the transactions that it spends from must also be confirmed. What happened here is that one of the transactions you are spending from is unconfirmed, in fact, it has even dropped from the network. Because that transaction is not confirmed, your transaction cannot confirm either, regardless of the fee and priority.

The issue here is that your wallet let you spend from an unconfirmed transaction. This should not happen with Bitcoin Core. The only way that this could happen is if it were spending from the change output of that transaction. This means that one of your recent spends must have not confirmed. Double check your transaction history and see if you see any recent spending transactions that has a low fee.
sr. member
Activity: 465
Merit: 309
The problem is that it is spending from a transaction that doesn't seem to exist, d890605be31f55e0ce8e748b4b056bc7841aecf51bc95d5d3445799606f85df1. This transaction appears to have been dropped, and because of this, your transaction cannot confirm.

You will not lose any Bitcoin. If the transaction confirms, then it goes to the destination. If it is dropped from the network, then it will be as if that transaction had never existed in the first place.

Thanks knight. Do you know what would cause this even though I paid the recommended fee and "did everything correct," per se? At least, I hope I did.

I'm seriously thinking about switching to another wallet... but not exactly sure if it's the wallet's fault. It's all kind of confusing and not very user friendly.

Also, do you have any idea of a brief ETA on how long the transaction will either reach its destination or drop and be refunded? It'll be refunded right? I'm trying to figure out what "...then it will be as if that transaction had never existed in the first place" means.

Ugh, sorry for all of the questions. This is just frustrating.
This address has not received any BTC https://live.blockcypher.com/btc/address/13q7zbhC788hhjRsnad8kgcGUQ5vmJp9CT/ and your transaction spends 0.02347996 BTC from that address.
full member
Activity: 210
Merit: 100
Hmm, I'm reading https://bitcointalksearch.org/topic/transaction-stuck-for-10-hours-used-bitcoin-core-1559125

Maybe I'll try that method since it worked for him. But I don't think I should have to do this when I used the recommended fee suggested by Bitcoin Core. Lol, it's all just so messy.
full member
Activity: 210
Merit: 100
The problem is that it is spending from a transaction that doesn't seem to exist, d890605be31f55e0ce8e748b4b056bc7841aecf51bc95d5d3445799606f85df1. This transaction appears to have been dropped, and because of this, your transaction cannot confirm.

You will not lose any Bitcoin. If the transaction confirms, then it goes to the destination. If it is dropped from the network, then it will be as if that transaction had never existed in the first place.

Thanks knight. Do you know what would cause this even though I paid the recommended fee and "did everything correct," per se? At least, I hope I did.

I'm seriously thinking about switching to another wallet... but not exactly sure if it's the wallet's fault. It's all kind of confusing and not very user friendly.

Also, do you have any idea of a brief ETA on how long the transaction will either reach its destination or drop and be refunded? It'll be refunded right? I'm trying to figure out what "...then it will be as if that transaction had never existed in the first place" means.

Ugh, sorry for all of the questions. This is just frustrating.
staff
Activity: 3374
Merit: 6530
Just writing some code
The problem is that it is spending from a transaction that doesn't seem to exist, d890605be31f55e0ce8e748b4b056bc7841aecf51bc95d5d3445799606f85df1. This transaction appears to have been dropped, and because of this, your transaction cannot confirm.

You will not lose any Bitcoin. If the transaction confirms, then it goes to the destination. If it is dropped from the network, then it will be as if that transaction had never existed in the first place.
full member
Activity: 210
Merit: 100
Hey all.

So, I'm having another issue with a BTC transaction from my Bitcoin Core wallet. This time it is for a larger amount and I think I did everything correct.

Now, I've made quite a few back and forth BTC transactions before with no issues, so I don't know what's going on this time around.

Here are the tx details:

Status: 0/unconfirmed
Date: 7/20/2016 15:43
To: 1FxQ7w5Y45a913tGqw22h9TLM1pbsXa1nc
Debit: -0.09900000 BTC
Transaction fee: -0.00011988 BTC
Net amount: -0.09911988 BTC
Transaction ID: 9965b1c9b0b4e9671b9a356200a8e1b17d987dbf7eed7dc7b6d1fb196aadf2ab-000

I chose the recommended transaction fee amount and it showed up as "High Priority" at first on blockchain.info, so just wondering why this happened:

"Transaction rejected by our node. Reason: Transaction was previously accepted but has been pruned from our database."

Only seeing the tx show up on this explorer at the moment:

https://live.blockcypher.com/btc/tx/9965b1c9b0b4e9671b9a356200a8e1b17d987dbf7eed7dc7b6d1fb196aadf2ab/

Do you guys have any recommendations?

I already tried a raw transaction push on https://btc.blockr.io/tx/push & https://coinb.in/#broadcast but they returned the following error codes (respectively):

"There was an error pushing your transaction to network! Did you sign your transaction? Is this double spend? Have you already sent this transaction?"

and

"Missing inputs"

Am I screwed? Should I just wait it out? If so, how long do you think it will take?

Should I try double spending, even though I'm not super technical when it comes to this stuff?

I guess the main question is will this transaction eventually go through to its destination (address owned by me) or returned to my wallet?? I just want to know the 0.099 BTC isn't totally lost! If so, that would really suck and make me a bit salty.

Thanks for reading and I hope someone can help me.
Jump to: