Topic: New BTC wallet, unconfirmed transactions, will tip best answer (Read 644 times)

The network got busy yesterday... the amount of unconfirmed transactions spiked from 5-10K to around 30K! And I see that today it even got as high as 45K a few hours ago... https://blockchain.info/charts/mempool-count

When this happens, fees go up and wait times increase... https://btc.com/stats/unconfirmed-tx

While a 102 sat/byte isn't necessarily "low" when you make the transaction... it's just that other people can stack on top and pay more, so you get pushed further down the queue... it happens sometimes... especially if there are large wait times between blocks (like 30 minutes+)... you end up with more and more transactions being added into the mempool... and if they pay a higher fee, they're likely to get higher priority.

It's change address. https://en.bitcoin.it/wiki/Change

Yes, I did the getraw ...., and the sendraw... - it returns the TXID, the same one I already had.
When I enter that TXID in a blockchain explorer, it returns "not found"

Does creating a new wallet, have a lower priority or something.  I even increased the network fee.


Are the logs in the logs in the debug log on a different time zone that the local machine?  Are they marked GMT?  Logs timestamps are off, some it appears

** Added info: in the Debug log, last lines
TimeStamp is in GMT
Relaying wtx "THE TXID"
ResendWalletTransactions: rebroadcast 1 unconfirmed transactions

Still no record showing up in BTC Block Explorer

*** More information added / updated
When I put my receive wallet in the block explorer, it is showing the 4 deposits, and then the 2 unconfirmed sends from earlier today.  I don't understand, why it shows additional sends to other addresses with those sends.  So I sent a small amount, to an exchange, .1 BTC.  The deposit address on the exchange looks right, then there's another address with a much larger BTC amount, to an address I don't recognize.

**** More information
1 of the transactions just got a confirmation.  The tx size is 225 the fee paid was .00022942 BTC that's 102sat per byte.  12hours to get 1 confirm.  Something is still not right, and I definitely don't understand this as well as I thought I did.  I think somehow the wallet got the time off, somehow, and it screwed up the transactions.

You mean it can't be found on a blockexplorer like blockchain.info?

Did you try the getrawtransaction/sendrawtransaction like I suggested? If so, what output did you get from sendrawtransaction?

Now is says unconfirmed, but the txid can't be found in search.  Maybe the wallet is corrupted at some level.

try using "getrawtransaction TRANSACTIONID" on the "Help -> Debug Window -> Console"...

then copy/paste the HEX code that it returns... and use "sendrawtransaction HEXCODE"

It seems like your transaction has been rejected by the network for some reason

I can, I guess, but ... in the meanwhile I sent another transaction.  With the new, old build.  It is now reading 0/Offline Has not been broadcast yet.  I have 7 connections to the BTC network. 

I've never had issues like this in 3years.  Running 14.2 QT 64bit on Windows 10.

It would be better if you can message me unconfirmed transaction id, I'll take a look. or even a screenshot will work.

OK - I fired up my other copy of my new wallet.  I moved the new wallet to another computer in the last few days.  This copy I brought up was going into cold storage.

I pulled up all 4 deposit transactions.  Checked the deposit txids.

They all show up as confirmed?!?  My recent transactions that would not confirm, are not there, but those deposit txids show up as fine.

So what would be the best test to make sure this wallet is working fine?  Attempt another send?

Do you know the transaction IDs of all 4 transactions?

I assume you should be able to find those transaction IDs in the new wallet.

If you have them, then you can check and see which (if any) of the 4 transactions are already confirmed.

You can look at those transaction IDs on a block explorer (such as blockr.io or blockchain.info) to see what fee your old wallet paid on the unconfirmed transactions.

Assuming that your old wallet paid a fee of at least 0.00000010 BTC per byte (10 satoshis per byte), you can submit the transaction IDs at the viabtc accellerator listed in escrow.ms's post above.

If your transactions paid a smaller fee than that, it may be a bit more complicated to get the transactions confirmed.

I'd have to restore my old wallet.  I thought everything was fine.  It was about a week ago now.  Once I saw everything confirmed in my new wallet, I thought all was fine.
The transactions were all the same, as far as the fee amount was whatever the wallet suggested.

So your suggesting, restoring the old wallet, and looking at the transactions?

If I read it properly I think Most probably when you sent bitcoins from you old wallet to your new wallet, you did not paid enough fees to cover up that transaction or some inputs were not confirmed. You need check transfer size and fees of your old wallet to new wallet transaction. If it's not confirmed you should try to submit it here https://pool.viabtc.com/tools/txaccelerator/

I started a new QT wallet before the fork.  Sent all my BTC to my new wallet from my older QT BTC wallet.  Everything looked fine with the 4 transactions.

The new wallet sync'd up fine, and confirmed the incoming deposits.  In the new wallet they are showing 900+ confirms now.  Tried to send some btc out today, and would not confirm.

I pulled up the txid of the outgoing transaction in the btc blockchain explorer, and it is showing no confirmations, but the txid shows up.  When I link to my wallet from the txid in the explorer, it is showing an unconfirmed balance, and 2 of the 4 transactions as unconfirmed. 

What is going on, and how do I correct it?

Did I shut down my old wallet too soon, did it need to run longer?