Topic: Bitcoin core not sending transaction (Read 1097 times)

It's not trivial to do, but I can prepare a raw transaction for you to sign, if you'd like. I would need more details like transaction IDs for that. Feel free to PM me.

Thanks for your help, I have managed to import the private keys over. Two transactions are showing as "Low fee" in Electrum and have not been confirmed, would you be able to help me solve this? I have never done double spend before, is this easy in Electrum?

Here is raw transaction:

01000000011ae62ee8edb2bc91092811718e62e446df3ff2c96f690031538f76770b7d4af600000 0006a47304402203bf3ce51eb40428e2269709e29a35f6843c75451c43f24be05bc413872058ae3 02204d0bcdac3b6690a48de56b1196d210c7b6a21198f1b578b0d8b0500856ddda2601210259045 e08384b68f7aade2f8f3fb4a4935f9493d5fc3d1ac963bbf3061b7e0a9ffeffffff02400d030000 0000001976a914290b759eaaec520bb62734514bf0e65d4b33937088ac7e554501000000001976a 914a0a2ebcb873988c45339ce2f97d7b47549b6f09688ac23260700

You should post the raw transaction here, so that users capable of decoding and analyzing these transactions can take a look and tell you if there are any issues that they see.

What should I do with the raw transaction?

I used right click on the transaction in the Bitcoin Core client and selected Copy Raw Transaction, is that the same as using the console?

Just a hunch, your transaction might be stuck because of your peers or your fees. It is a possibility that your peers might think that your transaction is non standard and refuse to broadcast it. Before touching your private keys, can you go to Help>Debug Window>Console and paste this: getrawtransaction . Replacing the txid accordingly.

Yes. Open bitcoin core, go to the debug window. If you have a passphrase on your wallet, type:


Then, for each address you'd like to transfer over, type:


Each time you do this, you will get a private key. Keep this secure. Don't post or share it with anyone.

Once you're done with this, open Electrum. Click file -> new/restore. Select standard wallet, use public or private keys. Paste ALL of the private keys you got from the previous step into the box, one per line. Click next, select a password, and you should then finally be all set.

Once you're done with that, go back to bitcoin core, and type walletlock into the debug window to lock the wallet again using the same passphrase.

Hi Hexafraction, yes could you instruct me on how to do that please?

That doesn't mean that you can't export the private key if push comes to shove and choose to use a different wallet program. You would have to type a few simple commands in the debug console to recover the private key from bitcoin core, and you could immediately paste it into Electrum's new wallet wizard (new wallet->standard wallet->use public/private keys). If you choose to do this, we can provide the commands needed.

I don't think I do, the transactions are not showing in my client since backup.

2017-05-28 20:22:57 CommitTransaction:
CTransaction(hash=c0ba6c4cf0, ver=1, vin.size=1, vout.size=2, nLockTime=468515)
    CTxIn(COutPoint(f64a7d0b77, 0), scriptSig=47304402203bf3ce51eb4042, nSequence=4294967294)
    CTxOut(nValue=0.00200000, scriptPubKey=76a914290b759eaaec520bb6273451)
    CTxOut(nValue=0.21321086, scriptPubKey=76a914a0a2ebcb873988c45339ce2f)
2017-05-28 20:22:57 keypool keep 6
2017-05-28 20:22:57 AddToWallet c0ba6c4cf04d21b743aa98d7b22f8c7b9d6ddfcb5a139cb3c1ed1392e2e6107c  new
2017-05-28 20:22:57 AddToWallet c0ba6c4cf04d21b743aa98d7b22f8c7b9d6ddfcb5a139cb3c1ed1392e2e6107c 
2017-05-28 20:22:57 Relaying wtx c0ba6c4cf04d21b743aa98d7b22f8c7b9d6ddfcb5a139cb3c1ed1392e2e6107c
2017-05-28 20:22:57 ProcessMessages: advertising address 79.66.221.154:8333
2017-05-28 20:22:57 receive version message: /Satoshi:0.14.1(UASF-SegWit-BIP148)/: version 70015, blocks=468599, us=79.66.221.154:65323, peer=5
2017-05-28 20:22:57 AdvertiseLocal: advertising address 79.66.221.154:8333
2017-05-28 20:23:31 UpdateTip: new best=0000000000000000000008c1e8206635a151c06fe984c6281f3d1f466790b366 height=468594 version=0x20000000 log2_work=86.503679 tx=226905014 date='2017-05-28 19:06:30' progress=0.999984 cache=29.4MiB(22664tx) warning='1 of last 100 blocks have unexpected version'
2017-05-28 20:23:31 ProcessMessages: advertising address 79.66.221.154:8333
2017-05-28 20:23:31 receive version message: /Satoshi:0.14.0/: version 70015, blocks=468599, us=79.66.221.154:65327, peer=6
2017-05-28 20:23:31 AdvertiseLocal: advertising address 79.66.221.154:8333
2017-05-28 20:24:37 UpdateTip: new best=0000000000000000011c42d07b32685cf6a2ecdc4b34b65a2b6f645f6f674c6d height=468595 version=0x20000000 log2_work=86.503713 tx=226906278 date='2017-05-28 19:29:27' progress=0.999988 cache=33.9MiB(28060tx) warning='1 of last 100 blocks have unexpected version'
2017-05-28 20:25:37 Pre-allocating up to position 0x400000 in rev00884.dat
2017-05-28 20:25:37 UpdateTip: new best=00000000000000000157c16b516e18ac242e505daea2fe7f171885928d614760 height=468596 version=0x20000000 log2_work=86.503747 tx=226908497 date='2017-05-28 19:52:28' progress=0.999993 cache=38.3MiB(33870tx) warning='1 of last 100 blocks have unexpected version'
2017-05-28 20:26:41 UpdateTip: new best=000000000000000001363a83263367a49576b8f49e8ee6f0912299dbf33ac8ad height=468597 version=0x20000000 log2_work=86.50378 tx=226911197 date='2017-05-28 19:53:42' progress=0.999993 cache=46.1MiB(39534tx) warning='1 of last 100 blocks have unexpected version'
2017-05-28 20:27:29 UpdateTip: new best=000000000000000000f5db108bf4959449353b2603a193a95d72f36f036b720c height=468598 version=0x20000000 log2_work=86.503814 tx=226913482 date='2017-05-28 20:12:54' progress=0.999997 cache=48.9MiB(44367tx) warning='1 of last 100 blocks have unexpected version'
2017-05-28 20:27:29 ProcessMessages: advertising address 79.66.221.154:8333
2017-05-28 20:27:29 receive version message: /Satoshi:0.14.0/: version 70015, blocks=468599, us=79.66.221.154:65366, peer=10
2017-05-28 20:27:29 AdvertiseLocal: advertising address 79.66.221.154:8333
2017-05-28 20:27:39 UpdateTip: new best=0000000000000000005f9c015623f4837c3cbe4743b42fb5eb74d125af46cc1f height=468599 version=0x20000002 log2_work=86.503848 tx=226915625 date='2017-05-28 20:14:33' progress=0.999997 cache=50.4MiB(47052tx) warning='1 of last 100 blocks have unexpected version'
2017-05-28 20:27:39 ProcessMessages: advertising address 79.66.221.154:8333
2017-05-28 20:27:39 receive version message: /Satoshi:0.13.99/: version 70015, blocks=468599, us=79.66.221.154:65369, peer=11
2017-05-28 20:27:39 AdvertiseLocal: advertising address 79.66.221.154:8333
2017-05-28 20:31:15 ProcessMessages: advertising address 79.66.221.154:8333
2017-05-28 20:31:15 receive version message: /Satoshi:0.13.2/: version 70015, blocks=468599, us=79.66.221.154:65409, peer=12
2017-05-28 20:31:15 AdvertiseLocal: advertising address 79.66.221.154:8333
2017-05-28 20:42:52 GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.
2017-05-28 20:47:39 GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.
2017-05-28 20:53:51 UpdateTip: new best=00000000000000000119bf644939bb3efae329dbd7fff960d74b1e2e8cae58a4 height=468600 version=0x20000000 log2_work=86.503881 tx=226918209 date='2017-05-28 20:53:16' progress=1.000000 cache=179.2MiB(59513tx) warning='1 of last 100 blocks have unexpected version'
2017-05-28 20:59:58 UpdateTip: new best=000000000000000001d35ce8562d66fea3622074beeadcb39f84269b81b4de46 height=468601 version=0x20000002 log2_work=86.503915 tx=226920854 date='2017-05-28 20:59:54' progress=1.000000 cache=197.6MiB(64393tx) warning='1 of last 100 blocks have unexpected version'
2017-05-28 21:06:20 Relaying wtx c0ba6c4cf04d21b743aa98d7b22f8c7b9d6ddfcb5a139cb3c1ed1392e2e6107c
2017-05-28 21:06:20 ResendWalletTransactions: rebroadcast 1 unconfirmed transactions
2017-05-28 21:06:24 UpdateTip: new best=0000000000000000016fec81066e8f9befb4642114cdc48b55029573a0f4c4dc height=468602 version=0x20000000 log2_work=86.503949 tx=226922611 date='2017-05-28 21:05:39' progress=1.000000 cache=202.1MiB(67293tx) warning='1 of last 100 blocks have unexpected version'

Just post as much as you can from the bottom of the file.

Sorry for being stupid, I tried to paste the debug log text but get error message 'The message exceeds the maximum allowed length (64000 characters)'

how do I post the file?

As long as you still have the private key for that address, even if transactions are not going through, you should still be able to export the key and use it with a different choice of wallet software, if it comes to that.

Please post your debug.log file.

I am having trouble sending transactions from my Bitcoin Core wallet. I am using Bitcoin Core version 0.14.1 (the latest version), 64 bit, Windows 10.

To be clear, this is not a case where I am getting unconfirmed transactions, its not even getting as far as that. The transactions (I have tried a few) do not even appear in Blockchain.info or other sites, they do not appear to be created at all, although the transaction and updated balance show on my client. My wallet is fully synced.

I have tried a few things to solve this problem. I have uninstalled and reinstalled the latest version of Bitcoin Core. I have deleted the entire blockchain and downloaded from scratch. I have also tried to install earlier versions of Bitcoin Core. When I rescan my backed-up wallet, the transactions have disappeared and my balance is back to what it was originally.

I have tried several transactions now, after rescanning my backed up wallet. Here is a screenshot of the latest transaction details:

https://puu.sh/w3RTa/97889b2d95.png

Sent to: 14k2S5k25mX2vbFhyNh4bPraexUNQebjRC
Transaction ID: c0ba6c4cf04d21b743aa98d7b22f8c7b9d6ddfcb5a139cb3c1ed1392e2e6107c

I also have an unconfirmed transaction, address 1Hvr56nfqPrP3WXGJ6DHuYRNCNyr4NygY2, this does not even display on my client anymore, could this be the problem?

Please  help, I'm worried that I've lost access to my funds.