3

to say this upfront: I know these kind of questions have been asked before, but I already tried some things and I really don't have the knowledge what to do next.

I recently tried to send an amount of BTC from a Bitcoin Core wallet. After one whole day, the transaction still has the status "0/unconfirmed, in memory pool" in Bitcoin Core. I've tried restarting with options (rescan; zapwallettxes), but it didn't work. I also used the dumpprivkey command and imported this key into a blockchain.info wallet. It says there's no money on it...

How can I get this money back?

screenshot of 'information'

Edit: Solved. Like Michael C Ippolito said, the transaction has been confirmed eventually. I thank you for your answers.

Improve this question
7
  • Weird. Does looking up the address (addresses start with 1abc...) on a different block explorer give you something different? How many blocks does your client have under Help -> Debug window -> Information -> Current number of blocks ?
    – Nick ODell
    Commented Nov 23, 2016 at 15:25
  • What exact differences am I looking for at blockchain/Block explorer?
    – user43501
    Commented Nov 23, 2016 at 17:34
  • A difference in balance.
    – Nick ODell
    Commented Nov 23, 2016 at 22:24
  • Balance is exactly the same. I guess the transaction ID is public anyway so I can post it here? 803d7b295895e1fffc0897ae55b1c26caa27b3bc237a87f22dc4cfc1f3e2bd57
    – user43501
    Commented Nov 24, 2016 at 3:04
  • 1
    Since the transaction wasn't confirmed yet, the receiving address didn't have a balance yet. That's to be expected. Blockchain.info's "High Priority" is a fixed limit of Satoshi/byte, unfortunately, they haven't fixed its behavior although it has been criticized for years that it isn't accurate.
    – Murch ♦
    Commented Nov 27, 2016 at 13:28

1 Answer 1

Reset to default
1

One cannot say for sure what is happening without seeing the transaction ID, but it's likely that this is being caused by the current transaction backlog of about 62,000 or so unconfirmed transactions.

If the transaction being discussed has a low fee (relative to the other 62,000 unconfirmed transactions) the transaction being discussed may not be confirmed until a large number of those other unconfirmed transactions have been confirmed.

Two possible outcomes are that the transaction is eventually confirmed or that the transaction will eventually get dropped from the network and you will still have control of those bitcoins.

EDIT: BIP 125 Opt-in Full Replace-by-Fee Signaling provides a flagging option for dealing with this, though I'm not sure if any Bitcoin clients currently provide userfriendly support for this.

Improve this answer
2
  • 1
    Right now these are getting more again. The link in the last paragraph, can I use this somehow?
    – user43501
    Commented Nov 24, 2016 at 15:52
  • Unfortunately not, except for with future transactions. From the BIP: "The opt-in full Replace-by-Fee (opt-in full-RBF) signaling policy described here allows spenders to add a signal to a transaction indicating that they want to be able to replace that transaction in the future."
    – Michael C Ippolito
    Commented Nov 25, 2016 at 21:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.