Topic: [GUIDE] Delete your 0/unconfirmed transactions in 30 seconds - page 3. (Read 49954 times)
This has happened with me also twice. This problem arises just because of network issues at that time, and what happens is that one transaction is displayed twice. This can be solved easily in most cases by a heavy refresh of your wallet, and if that doesn't solve, just make a new transaction, it will do a force refresh and probably fix problem. Alternatively, in last option you can contact your wallet provider for assistance. This will surely solve it out.
So this could be a way to delete unintentionally sent transactions? The only thing it needs is that it should have 9 confirmations, right?
But this methods could than be used as a scamming method too...
This is a way to delete transactions that are still shown on your client. The transaction should not have any confirmations for it to work and the mempool should have dropped your transaction already. AFAIK, only one doublespend was successful and it was during the march 2013 fork, the money was returned. But this methods could than be used as a scamming method too...
So this could be a way to delete unintentionally sent transactions? The only thing it needs is that it should have 9 confirmations, right?
But this methods could than be used as a scamming method too...
But this methods could than be used as a scamming method too...
cool thanks im gonna check this out
What about if using blockchain wallet. Is there anyway to delete transaction or maybe push it
IIRC, Blockchain.info does not rebroadcast transactions after it gets dropped out of mempool. You can push the transaction by getting the raw format at Code:
https://blockchain.info/tx/[insert tx here]?format=hex
Code:
https://blockchain.info/pushtx
But its show "Transaction Already Exists"
Is this done?
What about if using blockchain wallet. Is there anyway to delete transaction or maybe push it
IIRC, Blockchain.info does not rebroadcast transactions after it gets dropped out of mempool. You can push the transaction by getting the raw format at Code:
https://blockchain.info/tx/[insert tx here]?format=hex
Code:
https://blockchain.info/pushtx
But its show "Transaction Already Exists"
Is this done?
What about if using blockchain wallet. Is there anyway to delete transaction or maybe push it
IIRC, Blockchain.info does not rebroadcast transactions after it gets dropped out of mempool. You can push the transaction by getting the raw format at Code:
https://blockchain.info/tx/[insert tx here]?format=hex
Code:
https://blockchain.info/pushtx
What about if using blockchain wallet. Is there anyway to delete transaction or maybe push it
C:\Program Files\Bitcoin>bitcoin-qt.exe -zapwallettex doesn't seem to work on my Testnet wallet. I have a zero conf tx (mh1BnfNWBi6tY1RCC7vEu5DwCqDqKdVC2A) and it's still there in my transaction history. The testnet coins are somewhere in cyberspace now...
Any other methods, next to pywallet?
Any other methods, next to pywallet?
Has anyone tried this guide recently?
I tried the -zapwallettxes feature of the Bitcoin QT wallet, which does the exact same as the python trick: the unconfirmed transaction is gone from your wallet, and your balance seems to be restored.
BUT it won't allow you to double spend your bitcoins, you still need to wait for the network to drop (or confirm) your initial transaction.
I now really start to like this 'replace by fee' suggestion, there is a clear need to be able to increase the fee in case your transaction does not get confirmed quick enough.
Has anyone tried this guide recently?
Crazy !! , Thank you +1000
This might sound like a dumb question...but uhm why delete those unconfirmed transactions?...Sorry I am not really that much knowledgeable with the technical aspect of a lot of things...
no miner fee, double spend or anything is not valid in terms of transaction specs may cause unconfirmed transactions.
This might sound like a dumb question...but uhm why delete those unconfirmed transactions?...Sorry I am not really that much knowledgeable with the technical aspect of a lot of things...
I did all the steps as pointed out, but now get a message when i send a transaction that this is a potential double spend and the transaction is being rejected by the client.
It's polite to warn that yours is a necropost
.Wait some hours/days until the network forgets about your previous attempt. Then broadcast the new transaction.
I am sorry about that, had to look up the meaning of the word. Shall never happen again. So I guess I shall keep trying everyday to send and see what happens.
I did all the steps as pointed out, but now get a message when i send a transaction that this is a potential double spend and the transaction is being rejected by the client.
It's polite to warn that yours is a necropost
.Wait some hours/days until the network forgets about your previous attempt. Then broadcast the new transaction.
I did all the steps as pointed out, but now get a message when i send a transaction that this is a potential double spend and the transaction is being rejected by the client.
just worry about ssome error in send transaction . maybe will crash or will be put iit on
spend bitcoin yea.
spend bitcoin yea.
This is a useful tool. Great work! 
Some version settings for FRK and ADN
FRK - 35
ADN - 23
FRK - 35
ADN - 23
Jump to: