Topic: Unconfirmed Transaction - Requesting Help [SOLVED] (Read 288 times)

My wallet is claiming that my transactions went through, after two days of just letting it sit and performing the suggested actions of user Thirdspace.

Confirming COMPLETE

Topic Tx: Requested amount has been received to my ledger with 31 confirmations, and is proudly being displayed on the chrome ledger wallet app.
Wallet 1PEZ: Requested amount has been received with 31 confirmations.

I would like to thank you again user Thirdspace for your assistance. I'll make sure to +1 your rep, and if you'd like I want to tip you for your assistance.

I was hoping with offline mode, your wallet would not receive broadcast your old stuck transaction from other nodes
though the problem could be that your wallet still has the old tx in mempool despite -zap command
this "getrawtransaction" only needs to be done if you manage to re-create new tx and get a new txid but cannot broadcast it
and this can be done via debug > console and type the command there to get the hex rawtx
then push the rawtx manually to the network https://en.bitcoin.it/wiki/Transaction_broadcasting

in the case you want to try re-send them in a single transaction, it is called double spend attempt
since your transaction hasn't been confirmed, you haven't successfully sent to 1PEZ yet
so the utxo (fund) still belongs to 1H5h48KUB... and you can use it in a new tx

recommended network fee lately to be around 500s/B
but if you want to save a bit, you might want to try as low as ~350s/B (possible long wait or stuck again)
and I assume your new transaction would look something like this:
which would be around 636 bytes * 400s/B =~ 0.00254400 BTC tx fee , adjust the fee rate as you feel necessary
if you still have problems creating new tx, I can help you create the unsigned rawtx (if you trust me)
then you can use your wallet to verify the tx and sign it before broadcasting it yourself

Thank you for the information!


Yes, I ran -zapwallettxes=1, and -rescan, but i ran them separately and online. For example... I did -zap after it finished closed the program, edited the conf file to say -rescan and ran the program again. After it finished the -rescan I closed the program and edited the conf back to being blank then ran the program back up. I can give it a try offline to see if that does anything, but are you suggesting that i use both of them on the same line of text or would I put them on separate lines of text in the conf file? Also... for inputting i would do this offline or online, and are these two commands on separate lines of text or one line? What website do you recommend for brodcasting hex rawtxs? Lastly, by generating the tx offline would i get a new tx ID, and rawtx?


I think I'd rather attempt to send both my payments under a single transaction because i no longer need the 0.0048 going to the 1PEZ wallet in tx 20da23. Though from what i understand about transactions... I cannot redistribute these fund since i already "sent" them so that wallet 1PEZ receives them, and i cannot add it to my topics tx to move it to my ledger if I am able to "recover" the funds. Would i be correct?

I guess the ( in regards to the topic tx, because I am aware that i used a dreadfully low tx fee for the 0.0048 ) 0.00209585 BTC/kB recommended fee was not significant enough even though it costed around 75k satoshies. What fee would you recommend for this transaction?

I apologize for the multitude of questions, but I'm just trying to get an understanding on this subject so i can better myself ( and my transactions ) in the future!

Thanks again!  

that's how bitcoin works, unlike the way your conventional banking works.
when you "authorized" (make payment) of 0.0048, the wallet would use available utxo for sending out
though I'm not sure why it used more than enough inputs and why your destination address was the 2nd output
usually by default it would only use enough utxo for the amount transacted,
and the 1st address as the payment address then 2nd address for the change address

these addresses are what I called as change address as I mentioned above
it was auto generated by default by the wallet and you can't prevent it from happening again,
unlesss you enable coin select and setting/using custom (the same) change address every time you create new transactions

you did run -zapwallettxes=1 -rescan as arguments in the command line?
have you tried running it while offline, see if it helps... you can re-create the tx and then go online to send it
but make sure you get the hex rawtx by typing on console: getrawtransaction yournewtxid
so if it goes wrong again you can push/broadcast the hex rawtx manually to other nodes

You could just wait or like I said above, re-create the transaction with high enough tx fee
but this time you can make 2 payments (if it was your intention) at once in a single transaction (to save fee)

For the tx ID described in this topic, how can those two addresses have the BTC i owned in my 1H5h wallet to equal out the transaction i sent? When i sent the BTC during tx 20da23d639 I only authorized the 0.0048, and somehow that additional transaction I didn't authorize ( the 0.01 that when to 1FiN ) was tacked onto it. This was my first attempt at sending a tx, and chose the bare minimum fee as you may have saw. At the time i didn't mind the wait, but after a while of not getting it confirmed i essentially gave up on that tx ever coonfirming. That, i guess, was the first start of my wallet not correctly showing my balance.  Similar story for when I authorized a similar in size transaction (f944) i only intended to send the 0.0038, but then that 0.01 was sent to the 1Ha2fx "wallet" by being tacked onto this tx just like the first one. The only difference is that this tx was able to be confirmed. How did these two wallets ( 1FiN & 1Ha2 ) become into existence, and "secretly" have BTC sent to them without being shown in my tx log in my BTC Core wallet app? How can i prevent this from happening again?

Even if these two wallets are "working together" to get my topics tx come true... Would I just have to wait until it confirms, or would i have to somehow get a CPFP'd/double spend to make sure they go through?

Finally... when i run -zapwallettxes it does clear the unconfirmed txs and restores my wallet balance, but once i remove the command from the conf file and the wallet re-syncs the txs are immediately replaced and my balance goes to zero again. Suggestions?

Thanks Thirdspace for your research, and anyone else that helps me out in this matter.

No, it's not a double spent. It's simply a chained unconfirmed transactions.

inputs:
f944743572809016f7c30fc78253fc44db5a9e1a5ec7ee6f734531f60e750299 utxo-0 1Ha2fXwmp 0.01
20da23d6395450efa093eea2bea57ea8b6d488f6d83318f6040b23ddfd6777ef utxo-0 1FiN792w9 0.01 Unconfirmed

used in transaction:
954569e805861a70effa0be2505844413d7649619097013b41734789abd2f98d Your tx in this topic Unconfirmed


your input 1FiN792w9... is still unconfirmed in tx 20da23d639... and originated from

Well after running -zap i removed and saved the conf file to make sure dont zap it again. After the application booted up the transactions that were removed came back, and my balance is at back to where it was earlier. They were sent on their own (probably by the application), and now my moment of feeling like i saved myself has ended. Will update original posts with any new tx IDs that may have changed.

After some google searching i figured out how to do this, and i ran -zap and the bogus transactions that have been in my wallet are gone and all the respective satoshis are back as well!! Now.. what to do about that 0.01 btc that was sent to that weird address...

Ooh! TIL   


I'll do this and update you with results.


Yeah if they had access they would of had a nice haul from me, and my wallet would have displayed empty when it resynced. I've never exported the private key from this wallet to another, and we cannot rule out the possibility that this tx may have been made from another wallet with this address.

Thanks for your reply, and I'll see what i can do with this information!

If it doesn't exist, it's out of mempool already.

It seems your transaction somehow got double spent, and only one of them can get confirmed.

This is weird. I suggest to backup your wallet.dat, and start Bitcoin Core with command line options -zapwallettxes and -rescan. This removes all unconfirms transactions and reloads all confirmed transactions that belong to the addresses in your wallet.

Maybe. But what thief steals only a part of your coins?
Have you ever exported your private key? Can the transaction have been made from another wallet with the same address?

Doing some research on my own i found on https://blockchain.info/address/1Ha2fXwmpQn84kwYc4oqsjXj8irdEHiWRD that 0.01 BTC was sent to a wallet, from my wallet, that I've never seen or own. This may be contributing to why my current tx is not clearing since this transaction would leave me having a balance insufficient to fund the recent transaction I'm currently attempting.

This transaction does not appear in my BTC Core wallet either, and the last transaction my wallet displays was one that I've personally sent and confirmed.

So does this mean my wallet has been compromised?

Edit: At the time prior to me making my this transaction I had sufficient balance to make it, and my wallet was updated/synced before i sent the transaction.

I'm aware of that... Do you have any tips or suggestions?

Others I've asked so far said to just "wait it out" by letting the mempool forget it.

Your transaction id does not exist.

Bitcoin Client Software and Version Number: Bitcoin Core version v0.15.1 (64-bit)

Operating System: Windows 8.1 64-bit

System Hardware Specs: N/A

Description of Problem: I sent a transaction from my Bitcoin Core wallet to my Ledger Nano S, and with the recommended fee of 0.00209585 BTC/kB is still unconfirmed along with the transaction ID not being displayed on blockchain explorers.

Any Related Addresses
Receiving Address: 1LFAxyR6wzyKpE2qT9JHZ4qf2QWNKV41X2
Sending Address: 1H5h48KUB4bW9sp6bKQzNJE3oxvhfyo86

Any Related Transaction IDs: 954569e805861a70effa0be2505844413d7649619097013b41734789abd2f98d

Screenshot of the problem: N/A
Log Files from the Bitcoin Client: N/A
Status: Confirmed with 32 confirmations. Sent at 1/16/2018 19:08 (original 14:10 1/15/2018)

I recently got my ledger nano S, and after i went through the set up process i decided to send what i had in my BTC Core desktop wallet to it. when the ledger nano S told me to pick a block chain i chose Legacy, because I was unsure if Core added SegWit. I made sure the receiving address was correct before i clicked send, and I chose the recommended fee option that the application provides. My transaction did not appear on the Ledger Nano S chrome app at the time of sending, as well as of yet. Now it's stuck in "unconfirmed hell", and i'm sweatin' a bit. Block chain explorers say my Tx ID cannot be found as well. Do i wait for more blocks to be mined, or have i sent what i owned to a "Burn" address accidentally? The balance of my wallet has already been deducted so i cannot make a fee adjustment to the transaction. I attempted the same thing with my LTC core wallet after installing the ledger LTC wallet onto the nano. No problems, and was confirmed within minutes with the recommended fee option. The transaction appeared immediately even though it was not confirmed yet. I understand that LTC works differently than BTC, but i believe that i should have experienced roughly the same outcome with BTC.

Edit(s): Currently at a loss of what to do next... Guess I'll keep rescan-ing my wallet   ( 18:47, 1/15/2018 )
(1/16/2018) Strange thing is... When i sent some BTC that i purchased from an exchang to my Ledger it was confirmed, and properly stored into it like a normal transaction and the fee for the transaction was in total 0.0005 BTC. So it confused me on how this one went through but not the other, even with a lower amount payed in tx fee.   Either way... Time to do more research and try some stuff!
(1/20/2018) After performing some of the suggested actions brought up by user Thirdspace, and letting my wallet sync for a couple of days i can proudly announce that my transactions have been confirmed! 


Thank you for your time,
Bobflob