|
Title: Sending BTC Post by: spazzdla on 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?
Title: Re: Sending BTC Post by: franky1 on June 22, 2014, 12:09:42 AM yes.
simply check blockchain.info/address/the destination to see what its status is Title: Re: Sending BTC Post by: Brooker on June 22, 2014, 10:12:54 AM IS your wallet fully synched up, but like Franky said check the addresses on the blockchain.
Title: Re: Sending BTC Post by: Mayuyu48 on 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 addressplace 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 Title: Re: Sending BTC Post by: Ilsk on June 22, 2014, 10:44:25 AM Search your address on https://blockchain.info/ and see if the transaction is confirmed.
Title: Re: Sending BTC Post by: spazzdla on 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. Title: Re: Sending BTC Post by: Yeezus on June 22, 2014, 01:27:30 PM So they never got sent? Be careful as you might end up sending two payments.
Title: Re: Sending BTC Post by: Neg on 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. Title: Re: Sending BTC Post by: thecoindoctor on 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 manTitle: Re: Sending BTC Post by: InwardContour on 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. Title: Re: Sending BTC Post by: CEG5952 on 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. Title: Re: Sending BTC Post by: ranochigo on 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
Title: Re: Sending BTC Post by: InwardContour on 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. Title: Re: Sending BTC Post by: ranochigo on 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. Title: Re: Sending BTC Post by: spazzdla on 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. Title: Re: Sending BTC Post by: Swimpool on June 23, 2014, 04:21:30 PM If you use an old client you might need to upgrade it.
Title: Re: Sending BTC Post by: Velkro on 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. Title: Re: Sending BTC Post by: ranochigo on 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. Title: Re: Sending BTC Post by: Soappa on 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. Exactly. Bitcoin-qt, for example, will keep re-broadcasting your unconfirmed tx. Title: Re: Sending BTC Post by: spazzdla on 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. Security is the most important feature to me. I am using QT. Title: Re: Sending BTC Post by: spazzdla on June 24, 2014, 01:14:12 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. Exactly. Bitcoin-qt, for example, will keep re-broadcasting your unconfirmed tx. It will...? Didn't seem so.. Transaction number never showed up on blockchain.info soo.. I gave up and did what I did. Title: Re: Sending BTC Post by: Soappa on June 24, 2014, 01:24:50 PM Bitcoin-qt, for example, will keep re-broadcasting your unconfirmed tx. It will...? Didn't seem so.. Transaction number never showed up on blockchain.info soo.. I gave up and did what I did. Well, it should. Also, if you have the same problem next time, you could use getrawtransaction <TxID> and then push the transaction on https://blockchain.info/pushtx and https://blockr.io/tx/push Title: Re: Sending BTC Post by: Soappa on June 24, 2014, 01:28:23 PM I've already re-sent the BTC and re-downloaded the blockchain. Is sounds like you are using bitcoin-qt, don't. Multibit is a lot faster and easier. Multibit should be default client.It was synced with conections, I have a feeling it might of been because I closed the client before any confirms. Just for your reference: http://www.coindesk.com/multibit-user-loss-high-need-bitcoin-wallets/ Quote MultiBit’s response Wetseals accused MultiBit’s main developer Jim Burton of responding generically to the request, and not addressing the issue. Later, Burton commented on Reddit: “In the life of MultiBit (i.e from 2011) there’s probably a handful of cases like these. If there is damage to the private key bytes (for whatever reason) and there is no other copy available/backed up then you’ve lost access to the bitcoins.” Title: Re: Sending BTC Post by: spazzdla on June 24, 2014, 01:36:45 PM Bitcoin-qt, for example, will keep re-broadcasting your unconfirmed tx. It will...? Didn't seem so.. Transaction number never showed up on blockchain.info soo.. I gave up and did what I did. Well, it should. Also, if you have the same problem next time, you could use getrawtransaction <TxID> and then push the transaction on https://blockchain.info/pushtx and https://blockr.io/tx/push Sweet, this is good info, thanks man!! Title: Re: Sending BTC Post by: Soappa on June 24, 2014, 01:39:37 PM Bitcoin-qt, for example, will keep re-broadcasting your unconfirmed tx. It will...? Didn't seem so.. Transaction number never showed up on blockchain.info soo.. I gave up and did what I did. Well, it should. Also, if you have the same problem next time, you could use getrawtransaction <TxID> and then push the transaction on https://blockchain.info/pushtx and https://blockr.io/tx/push Sweet, this is good info, thanks man!! No problem, and I hope you don't need to use that though. :P Title: Re: Sending BTC Post by: monsterbitty on June 24, 2014, 01:48:23 PM Did you checked the balance in the new address using blockchain.info/address/Youraddress.
so you can track the status. Title: Re: Sending BTC Post by: spazzdla on June 24, 2014, 03:22:25 PM Did you checked the balance in the new address using blockchain.info/address/Youraddress. so you can track the status. I have, I have also checked it on my seperate HD where my one wallet is located(well...I've also got it on 6-7 USB's but that is neither here or there). It is completely offline now though. |