spazzdla (OP)
Legendary
 Offline
Activity: 1722
Merit: 1000
|
 |
June 22, 2014, 12:08:07 AM |
|
I sent some BTC from one hard drive, it has been in transaction for a bit and still not sent 2.2milliBTC fee too!!. I changed over to my other hard drive and it doesn't show the transaction. Is that because it has not been verified in the blockchain?
|
|
|
|
|
franky1
Legendary
Offline
Activity: 4228
Merit: 4500
|
|
June 22, 2014, 12:09:42 AM |
|
yes.
simply check blockchain.info/address/the destination
to see what its status is
|
I DO NOT TRADE OR ACT AS ESCROW ON THIS FORUM EVER.
Please do your own research & respect what is written here as both opinion & information gleaned from experience. many people replying with insults but no on-topic content substance, automatically are 'facepalmed' and yawned at
|
|
|
|
Brooker
|
|
June 22, 2014, 10:12:54 AM |
|
IS your wallet fully synched up, but like Franky said check the addresses on the blockchain.
|
|
|
|
|
|
Mayuyu48
|
|
June 22, 2014, 10:25:21 AM |
|
I sent some BTC from one hard drive, it has been in transaction for a bit and still not sent 2.2milliBTC fee too!!. I changed over to my other hard drive and it doesn't show the transaction. Is that because it has not been verified in the blockchain?
where's your bitcoin address place it here, so we can see what is the problem maybe too many few transaction make the transcation size become bigger so it needs more time to confirm |
|
|
|
Ilsk
Legendary
Offline
Activity: 833
Merit: 1015
|
|
June 22, 2014, 10:44:25 AM |
|
Search your address on https://blockchain.info/ and see if the transaction is confirmed. |
|
|
|
|
spazzdla (OP)
Legendary
Offline
Activity: 1722
Merit: 1000
|
|
June 22, 2014, 12:23:03 PM |
|
IS your wallet fully synched up, but like Franky said check the addresses on the blockchain.
It fucked up some how... *shrugs* I just wipped out the blockchain and started re-downloading, Transaction does not show up on blockchain. I just resent the coins from my second harddrive *shrugs* w/e. |
|
|
|
|
|
Yeezus
|
|
June 22, 2014, 01:27:30 PM |
|
So they never got sent? Be careful as you might end up sending two payments.
|
|
|
|
|
Neg
|
|
June 22, 2014, 01:28:40 PM |
|
IS your wallet fully synched up, but like Franky said check the addresses on the blockchain.
It fucked up some how... *shrugs* I just wipped out the blockchain and started re-downloading, Transaction does not show up on blockchain. I just resent the coins from my second harddrive *shrugs* w/e. Try use a wallet that doesnt download the entire blockchain. It's a pain having to update it all the time. |
|
|
|
|
thecoindoctor
Newbie
Offline
Activity: 48
Merit: 0
|
|
June 22, 2014, 01:49:34 PM |
|
I sent some BTC from one hard drive, it has been in transaction for a bit and still not sent 2.2milliBTC fee too!!. I changed over to my other hard drive and it doesn't show the transaction. Is that because it has not been verified in the blockchain?
Damn that sucks man |
|
|
|
|
|
InwardContour
|
|
June 22, 2014, 08:56:19 PM |
|
Do you have either of the addresses that you sent the BTC to/from or the TX id?
If a TX is not confirmed by the network after 24 hours the nodes will "forget" the TX and the BTC will remain in the address that you tried to send it from.
|
|
|
|
|
|
CEG5952
|
|
June 22, 2014, 09:21:39 PM |
|
If a TX is not confirmed by the network after 24 hours the nodes will "forget" the TX and the BTC will remain in the address that you tried to send it from.
That's not entirely true. I've had unconfirmed transactions (specifically, those sent without fee), that have been unconfirmed for 2-3 days, but eventually were confirmed. So I'm not sure what the hard-and-fast rules are here. |
|
|
|
ranochigo
Legendary
Offline
Activity: 2982
Merit: 4193
|
|
June 23, 2014, 03:15:07 AM |
|
Do you have nodes connecting to your client? Is your blockchain fully synced? Try searching on blockr.io
|
|
|
|
|
InwardContour
|
|
June 23, 2014, 04:49:06 AM |
|
If a TX is not confirmed by the network after 24 hours the nodes will "forget" the TX and the BTC will remain in the address that you tried to send it from.
That's not entirely true. I've had unconfirmed transactions (specifically, those sent without fee), that have been unconfirmed for 2-3 days, but eventually were confirmed. So I'm not sure what the hard-and-fast rules are here. This may have been an exception to the rule. My understanding of the Bitcoin protocol is that nodes should delete unconfirmed TX after 24 hours. I looked on google to double check and couldn't find anything concrete. One thing you could do to take care of this issue would be to send a TX that uses at least one of the same inputs as the unconfirmed TX with a bigger fee and this should be confirmed by the network. |
|
|
|
|
ranochigo
Legendary
Offline
Activity: 2982
Merit: 4193
|
|
June 23, 2014, 04:53:52 AM |
|
If a TX is not confirmed by the network after 24 hours the nodes will "forget" the TX and the BTC will remain in the address that you tried to send it from.
That's not entirely true. I've had unconfirmed transactions (specifically, those sent without fee), that have been unconfirmed for 2-3 days, but eventually were confirmed. So I'm not sure what the hard-and-fast rules are here. This may have been an exception to the rule. My understanding of the Bitcoin protocol is that nodes should delete unconfirmed TX after 24 hours. I looked on google to double check and couldn't find anything concrete. One thing you could do to take care of this issue would be to send a TX that uses at least one of the same inputs as the unconfirmed TX with a bigger fee and this should be confirmed by the network. Different clients have different behaviour, some rebroadcast for a long time if it remains unconfirmed. Some stop broadcasting after a period of time. |
|
|
|
spazzdla (OP)
Legendary
Offline
Activity: 1722
Merit: 1000
|
|
June 23, 2014, 01:03:43 PM |
|
Do you have nodes connecting to your client? Is your blockchain fully synced? Try searching on blockr.io
I've already re-sent the BTC and re-downloaded the blockchain. It was synced with conections, I have a feeling it might of been because I closed the client before any confirms. |
|
|
|
|
Swimpool
Newbie
Offline
Activity: 22
Merit: 0
|
|
June 23, 2014, 04:21:30 PM |
|
If you use an old client you might need to upgrade it.
|
|
|
|
|
Velkro
Legendary
Offline
Activity: 2296
Merit: 1014
|
|
June 23, 2014, 06:15:44 PM |
|
I've already re-sent the BTC and re-downloaded the blockchain.
It was synced with conections, I have a feeling it might of been because I closed the client before any confirms.
Is sounds like you are using bitcoin-qt, don't. Multibit is a lot faster and easier. Multibit should be default client. |
|
|
|
|
ranochigo
Legendary
Offline
Activity: 2982
Merit: 4193
|
|
June 24, 2014, 02:09:08 AM |
|
Do you have nodes connecting to your client? Is your blockchain fully synced? Try searching on blockr.io
I've already re-sent the BTC and re-downloaded the blockchain. It was synced with conections, I have a feeling it might of been because I closed the client before any confirms. Shouldn't be so, try to see the address at blockr.io. Once you send it, the nodes will broadcast it among the network. You can try to wait for a few minutes before closing it. |
|
|
|
|
Soappa
|
|
June 24, 2014, 12:48:15 PM |
|
If a TX is not confirmed by the network after 24 hours the nodes will "forget" the TX and the BTC will remain in the address that you tried to send it from.
That's not entirely true. I've had unconfirmed transactions (specifically, those sent without fee), that have been unconfirmed for 2-3 days, but eventually were confirmed. So I'm not sure what the hard-and-fast rules are here. This may have been an exception to the rule. My understanding of the Bitcoin protocol is that nodes should delete unconfirmed TX after 24 hours. I looked on google to double check and couldn't find anything concrete. One thing you could do to take care of this issue would be to send a TX that uses at least one of the same inputs as the unconfirmed TX with a bigger fee and this should be confirmed by the network. Different clients have different behaviour, some rebroadcast for a long time if it remains unconfirmed. Some stop broadcasting after a period of time. Exactly. Bitcoin-qt, for example, will keep re-broadcasting your unconfirmed tx. |
|
|
|
spazzdla (OP)
Legendary
Offline
Activity: 1722
Merit: 1000
|
|
June 24, 2014, 01:13:08 PM |
|
I've already re-sent the BTC and re-downloaded the blockchain.
It was synced with conections, I have a feeling it might of been because I closed the client before any confirms.
Is sounds like you are using bitcoin-qt, don't. Multibit is a lot faster and easier. Multibit should be default client. Security is the most important feature to me. I am using QT. |
|
|
|
|
|
