Bitcoin Forum
November 18, 2024, 05:54:43 PM *
News: Check out the artwork 1Dq created to commemorate this forum's 15th anniversary
 
   Home   Help Search Login Register More  
Pages: [1] 2 »  All
  Print  
Author Topic: 0 confirmations after 2 days. Need help  (Read 5439 times)
wheelz1200 (OP)
Legendary
*
Offline Offline

Activity: 3780
Merit: 1418



View Profile
December 14, 2015, 11:37:59 PM
 #1

So I was using qt-wallet 0.10.0 when I sent 2 transactions.  One for ~.66 and one for .026 to another wallet I have.  These transactions have stayed unconfirmed.  I paid minor tx fees fro both and this is the very first time this has happened to me.  Shortly thereafter the wallet had a warning saying I needed to update my wallet.  I have since downloaded 0.11.2  and it still hasnt confirmed.  the 2 transaction IDs are below:

1) d02f3400a1c174463b166b1b622700c78806452519c370e3868f07f234b0585b-000  (for .66 and a 0.00003371 transaction fee)
2) 3f88274cae5ec846cf954071c95be196d75d20686e708ea5b0c1a6ba2f254edc-000 (for .026 plus 0.00000229 transaction fee)

Can someone help me with pushing these transactions through or reclaiming the amount on my qt wallet so that I can resend.  Thanks.
DarkStar_
Legendary
*
Offline Offline

Activity: 2772
Merit: 3284


View Profile WWW
December 14, 2015, 11:42:47 PM
 #2

So first you should probably use a fee of at least 0.0001 BTC
Anyway, the sticked thread should be able to help you with your problem.
(https://bitcointalk.org/index.php?topic=232979.0)

taking a break - expect delayed responses
wheelz1200 (OP)
Legendary
*
Offline Offline

Activity: 3780
Merit: 1418



View Profile
December 14, 2015, 11:52:39 PM
 #3

I know i just always used what the qt wallet had set on it.  Thanks will look into that
wheelz1200 (OP)
Legendary
*
Offline Offline

Activity: 3780
Merit: 1418



View Profile
December 15, 2015, 12:02:48 AM
 #4

So first you should probably use a fee of at least 0.0001 BTC
Anyway, the sticked thread should be able to help you with your problem.
(https://bitcointalk.org/index.php?topic=232979.0)

So do you think I should sit tight.  Do you think these transactions will get picked up with a lower tx fee then .0001?  If I have to resend with increased tx fee that seems a little difficult after reading.  Is it easier then it reads?  Sorry just not as technically competent than most people here.  Thanks for the help and insight.
Mikestang
Legendary
*
Offline Offline

Activity: 1274
Merit: 1000



View Profile
December 15, 2015, 12:16:57 AM
 #5

I think when you input a tx fee you may have done a total fee instead of fee/kb, because your tx fees are super small.  Those tx will get picked up eventually, I think you just need to wait it out.
wheelz1200 (OP)
Legendary
*
Offline Offline

Activity: 3780
Merit: 1418



View Profile
December 15, 2015, 12:26:49 AM
 #6

I think when you input a tx fee you may have done a total fee instead of fee/kb, because your tx fees are super small.  Those tx will get picked up eventually, I think you just need to wait it out.

OK I will  I checked the one transaction on blockchain 3f88274cae5ec846cf954071c95be196d75d20686e708ea5b0c1a6ba2f254edc-000

and the message I get is "unrecognized search pattern" what does that mean?  Also Ive sent another small transaction .005 and that one already has 2 confirmations.  Is that normal that some do not but then follow on transactions can get sent?

Note: When I sent these 2 days ago to my coinbase wallet, the coinbase wallet had them as pending, and now they are not showing as pending or anything?  Is that normal as well.  I think Im going to wait a couple more days ~5 and then try something else.  Does that seem a good amount of time to wait?
funkydog
Full Member
***
Offline Offline

Activity: 140
Merit: 100



View Profile
December 15, 2015, 07:49:27 AM
 #7

Here is your first transaction:

https://blockchain.info/tx-index/d02f3400a1c174463b166b1b622700c78806452519c370e3868f07f234b0585b

As you can see its "Low Priority"... because your fee is only 0.00003371 BTC. Next time make sure the minimum fee is 0.0001 BTC.
ivanst776
Legendary
*
Offline Offline

Activity: 1540
Merit: 1003



View Profile
December 15, 2015, 08:49:59 PM
 #8

I have a feeling that you will wait 2-3 days and the money will be send back to the sender, this because the fees are bery low and the tx has been marked as (Low Priority)
shorena
Copper Member
Legendary
*
Offline Offline

Activity: 1498
Merit: 1540


No I dont escrow anymore.


View Profile
December 15, 2015, 09:06:29 PM
 #9

I have a feeling that you will wait 2-3 days and the money will be send back to the sender, this because the fees are bery low and the tx has been marked as (Low Priority)

Thats not how bitcoin core works. It rebroadcasts the TX so the network does not forget about it. OP would have to remove the TX for that to stop.

Im not really here, its just your imagination.
OnkelPaul
Legendary
*
Offline Offline

Activity: 1039
Merit: 1005



View Profile
December 15, 2015, 09:30:24 PM
 #10

The transaction 3f88274cae5ec846cf954071c95be196d75d20686e708ea5b0c1a6ba2f254edc simply has a somewhat low fee, it should be mined eventually when miners have enough spare room in blocks to accomodate transactions with low or no fees.
The other transaction has one unconfirmed input from the first transaction, and it can not be mined before the other one has been mined (can be in the same block).
You probably can't do much about it now, but to avoid similar situations you might enable a setting in your wallet so that only confirmed transaction outputs are used as inputs.
The other thing that you could consider is to create a single transaction when you want to send to two recipients at about the same time, which seems to be the case here. Iif you do that, your transaction fee could be a little higher since you're only paying for one transaction.

Onkel Paul

langedwig
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
December 16, 2015, 02:07:06 AM
 #11

So I was using qt-wallet 0.10.0 when I sent 2 transactions.  One for ~.66 and one for .026 to another wallet I have.  These transactions have stayed unconfirmed.  I paid minor tx fees fro both and this is the very first time this has happened to me.  Shortly thereafter the wallet had a warning saying I needed to update my wallet.  I have since downloaded 0.11.2  and it still hasnt confirmed.  the 2 transaction IDs are below:

1) d02f3400a1c174463b166b1b622700c78806452519c370e3868f07f234b0585b-000  (for .66 and a 0.00003371 transaction fee)
2) 3f88274cae5ec846cf954071c95be196d75d20686e708ea5b0c1a6ba2f254edc-000 (for .026 plus 0.00000229 transaction fee)

Can someone help me with pushing these transactions through or reclaiming the amount on my qt wallet so that I can resend.  Thanks.

The transaction fees are so low that the transaction will not confirm ever or get rejected.
Why didnot you send it with some more higher fees ? you included such a minor fees
Because of it you could face problems !
diodio1
Sr. Member
****
Offline Offline

Activity: 285
Merit: 250



View Profile WWW
December 16, 2015, 02:12:19 AM
 #12

Quote
1) d02f3400a1c174463b166b1b622700c78806452519c370e3868f07f234b0585b-000  (for .66 and a 0.00003371 transaction fee)
2) 3f88274cae5ec846cf954071c95be196d75d20686e708ea5b0c1a6ba2f254edc-000 (for .026 plus 0.00000229 transaction fee)
Both of the transactions are still unconfirmed due  to very minor fees , no miners will confirm unless all high fee transactions are cleared , i think you will surely get them to spend again.

BurHan Alassad
Norther front commander for web security in Syrian Electronic ARMY.
wheelz1200 (OP)
Legendary
*
Offline Offline

Activity: 3780
Merit: 1418



View Profile
December 16, 2015, 06:28:10 AM
 #13

Here is your first transaction:

https://blockchain.info/tx-index/d02f3400a1c174463b166b1b622700c78806452519c370e3868f07f234b0585b

As you can see its "Low Priority"... because your fee is only 0.00003371 BTC. Next time make sure the minimum fee is 0.0001 BTC.

Thanks All for your input I really appreciate it.  As for the first transaction its now when I go on the blockchain it now says:

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


What does this mean?
diodio1
Sr. Member
****
Offline Offline

Activity: 285
Merit: 250



View Profile WWW
December 16, 2015, 06:32:11 AM
 #14



Thanks All for your input I really appreciate it.  As for the first transaction its now when I go on the blockchain it now says:

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


What does this mean?

Blockchain removed your Transaction from its database due to unconfirmed status , if you are using blockchan.info then those BTC would be available to you for reuse.

BurHan Alassad
Norther front commander for web security in Syrian Electronic ARMY.
wheelz1200 (OP)
Legendary
*
Offline Offline

Activity: 3780
Merit: 1418



View Profile
December 16, 2015, 07:34:32 PM
 #15

looks like my coinbase wallet is showing it as pending receipt again.  My qt core wallet must have rebroadcast the transaction?

Look up the transaction again and its showing low priority. So I guess at this point I pray that someone takes pity on me and adds it to their block all due to the low transaction fee that was put on it?

https://blockchain.info/tx/d02f3400a1c174463b166b1b622700c78806452519c370e3868f07f234b0585b

wheelz1200

Chemistry1988
Legendary
*
Offline Offline

Activity: 1120
Merit: 1000


View Profile
December 16, 2015, 07:59:45 PM
 #16

Can someone help me with pushing these transactions through or reclaiming the amount on my qt wallet so that I can resend.  Thanks.

If you want to remove those unconfirmed transactions from your bitcoin core wallet, run your bitcoin core with -zapwallettxes=1. It will delete all your wallet transactions and do a rescan. The process will take some time to complete, much longer if you are using an old machine though.
wheelz1200 (OP)
Legendary
*
Offline Offline

Activity: 3780
Merit: 1418



View Profile
December 17, 2015, 01:55:09 AM
 #17

Can someone help me with pushing these transactions through or reclaiming the amount on my qt wallet so that I can resend.  Thanks.

If you want to remove those unconfirmed transactions from your bitcoin core wallet, run your bitcoin core with -zapwallettxes=1. It will delete all your wallet transactions and do a rescan. The process will take some time to complete, much longer if you are using an old machine though.

Thanks, looks like I might have to go that route.  Can you explain how I would go about "run your bitcoin core with -zapwallettxes=1".  Thanks

Note:  I sent another test transaction to my coinbase wallet from the core wallet and it went through.  But the amount shows in red in my core wallet, why is it in red, will that clear up if I remove my unconfirmed transactions?
ranochigo
Legendary
*
Offline Offline

Activity: 3038
Merit: 4420


Crypto Swap Exchange


View Profile
December 17, 2015, 04:34:21 AM
 #18

Can someone help me with pushing these transactions through or reclaiming the amount on my qt wallet so that I can resend.  Thanks.

If you want to remove those unconfirmed transactions from your bitcoin core wallet, run your bitcoin core with -zapwallettxes=1. It will delete all your wallet transactions and do a rescan. The process will take some time to complete, much longer if you are using an old machine though.

Thanks, looks like I might have to go that route.  Can you explain how I would go about "run your bitcoin core with -zapwallettxes=1".  Thanks

Note:  I sent another test transaction to my coinbase wallet from the core wallet and it went through.  But the amount shows in red in my core wallet, why is it in red, will that clear up if I remove my unconfirmed transactions?
If you're using Windows, go to run and type CMD. Next, use
Code:
"C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe" -zapwallettxes
or
Code:
"C:\Program Files\Bitcoin\bitcoin-qt.exe" -zapwallettxes
. This would remove any unconfirmed transaction from the client and prevent it from automatically rebroadcasting. The transaction would not be automatically forgotten by mempool on immediately but it would take sometime. After a day or two, most nodes would have forgotten about your transaction and you can continue to remake a new one.

Regarding your red amount, the BTC was deducted from your client and hence it would be red. It would stay red and you do not need to worry.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
wheelz1200 (OP)
Legendary
*
Offline Offline

Activity: 3780
Merit: 1418



View Profile
December 17, 2015, 05:00:21 AM
 #19

Can someone help me with pushing these transactions through or reclaiming the amount on my qt wallet so that I can resend.  Thanks.

If you want to remove those unconfirmed transactions from your bitcoin core wallet, run your bitcoin core with -zapwallettxes=1. It will delete all your wallet transactions and do a rescan. The process will take some time to complete, much longer if you are using an old machine though.

Thanks, looks like I might have to go that route.  Can you explain how I would go about "run your bitcoin core with -zapwallettxes=1".  Thanks

Note:  I sent another test transaction to my coinbase wallet from the core wallet and it went through.  But the amount shows in red in my core wallet, why is it in red, will that clear up if I remove my unconfirmed transactions?
If you're using Windows, go to run and type CMD. Next, use
Code:
"C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe" -zapwallettxes
or
Code:
"C:\Program Files\Bitcoin\bitcoin-qt.exe" -zapwallettxes
. This would remove any unconfirmed transaction from the client and prevent it from automatically rebroadcasting. The transaction would not be automatically forgotten by mempool on immediately but it would take sometime. After a day or two, most nodes would have forgotten about your transaction and you can continue to remake a new one.

Regarding your red amount, the BTC was deducted from your client and hence it would be red. It would stay red and you do not need to worry.

Ok I ran the second set of code you gave me from the command line.  Client opened up and those 2 transactions are still on my client, will this take some time to be removed from my wallet and is it automatic? If/when they are removed I guess the bitcoin amount will show back up in my balance to be able to spend again? How can I find out when this transaction was erased from the mem pool? Also should I keep my client open to make this process or could I shut it down?  Sorry for the questions but this has really gotten me into a loop for a couple of days. 

Oh and for the reduction in red...complete brain shut down, I guess Im just worried about the unconfirmed trans and see red and assumed an issue.  I generally use the core for my mining proceeds coming in and don't use it as a hot wallet. 

Thanks for your help and hopefully this will be resolved soon.
Quickseller
Copper Member
Legendary
*
Offline Offline

Activity: 2996
Merit: 2374


View Profile
December 17, 2015, 06:13:38 AM
 #20

Review and sign the below transaction
Code:
0100000019e7b53e5b24da2c1e8b95c440614964fcafdfe3a5711740e90b6f7a2fae89e0df760000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff229fb55ee012117db1ff088069e371bd28f242ab3706a99717a913954570bcd7730000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff9f64ec1ea8c1112787cd13e0bb88933a3f9a20bf216f28fd47fdc3967cb1091d7c0000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff07ce62f98b0733d924a294098b853486a7b66c6e5814414b7f3a49edb30cb04d740000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffffd7f1a5ce76e21245b721c118920d0d788dca003e55cf6e04171c8d8154358c1a760000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff56f84212d14341380b84b7167145be598a4205cede7454b5a93b4af515e4de81750000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffffc18f6d09e8b0a7abe7640a693552675c0cfd43be675a3bfcbacdeb96f0ad46536f0000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff673d2156159f0b576afdd2d5f1016331d5fbb3dd661f746edd8b01a68c0a5101800000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff6377df4346729d236f4fc9532f578f4883e498794173bc4c29c2fe8084e6cb8d750000001976a9143c76470255291728495d01c936a3159bdb895e0e88acfffffffff7f4eba3cd508ccd5aad419e1748d6e0e337af08bc442d3eaa38dc5eac0e25277d0000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff698e547c6a1151c0ac713ef4af911d51298889f813f628f999ab99c3c9d8a940760000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffffd4e4c0e09a2e0220f999bd7408d38587654ab63c5013c9a12dd707340fcf41b8800000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffffc74ef9ac8bad4c0eb69c828a02cb9ae3cd8cb8e379e4b052c50da1f8fa68f14a760000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff59b4133f09f805a87412e75f7c4c490aca692073b69f7dcaf3b026a3fa9f48fd890000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff73ad484ca618fa80731aa2676420cd65a47e4de677196aac8ab6e638b787877c6f0000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff6e270a6f19824f8982cd65afc66f2bebdab2943c15a86fde96642494c3b888b8870000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff85da44b1804bc6bc389785504412a3e1d6d7bfd81ef6dac751aef85e40461768740000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffffb037b98adbb08a74d5a458b0fcc2ba832dce14262a32f7eaf1fe1b0782499ff1770000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff807493cd7575e81f297bd2004394a8364101bd207b2a5d5ebc1a8465fd38f9d8850000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff37aa74498cbf8421379d1a7a9f258eb8279e9ef8c3e181f1ed99ce54b9f7ba2c840000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff18584445e321c2a813c9127c25f89b1d844d9a0dfbe3c15f587516d0a6a27688770000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff2c858048991079c08675ad18917e035de9705747c79c78446a71deed3ffc8906780000001976a9143c76470255291728495d01c936a3159bdb895e0e88acfffffffffc9df0f4ea178d86f7a7286498ee2d41ebd63305415919486bd851df9c833470670000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff919f5cb452d1e23b07ef8a6116bde026ddcc3ca1b8f6731ab1f76435bc873d15770000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffffc4279598a1ad240663e0fa793c18a1bbbbc52c0b720a274ce0eb6328b229fa678b0000001976a9143c76470255291728495d01c936a3159bdb895e0e88acffffffff01f7a0ae04000000001976a9143c76470255291728495d01c936a3159bdb895e0e88ac00000000

The above transaction should double spend both transactions in question. You should be able to sign the tx even if it conflicts with what is in your mempool of bitcoin core. After you sign the transaction, you are going to want to shut down bitcoin core so it will stop rebroadcasting the transaction.

You can either post or PM me the signed transaction and I will broadcast it for you, and hopefully it will get confirmed.

★ ★ ██████████████████████████████[█████████████████████
██████████████████████████████████████████████████████████████████████
██████████████████████████████████████████████████████████████████
███████████████████████████████████████████████████████████████████
████████████████████████████████████████████████████████████████████
██████████████████████████████████████████████████████████████████
███████████████████████████████████████████████████████████████████
█████████████████████████████████████████████████████████████████████
█████████████████████████████████████████████████████
██████████████████████████████████████████████████████████████████
█████████████████████████████████████████████████████████████
████████████████████████████████████████████████████████████
███████████████████████████████████████████████████████████████████
★ ★ 
Pages: [1] 2 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!