I read the reviews... and most of them seemed to be blaming the app for slow confirmation times... pretty much like the reviews for all wallet software.

Most people don't understand the way Bitcoin really works and get all pissy at their wallet software for their transactions not being confirmed.

I haven't given the wallet a super thorough test, but it offers 2 options for fees...



The top option seems to be "dynamic" and is currently ~289 sats/byte so should be "OK"... I'm guessing all the idiots whining are using the 0.0001 fee per kB option... which is like 10 sats/byte

Seems like there are only 2 unspent TXes in that address...

12NcNYb2oEh6ANo95AakEjPqQdgbcxh4m9 - (Unspent) 0.01059718 BTC
12NcNYb2oEh6ANo95AakEjPqQdgbcxh4m9 - (Unspent) 0.00181643 BTC

(2 * 148) + (1 * 34) + 10 = 340 bytes

340 * 60 = 20400 sats

So, send (0.01241361 - 0.00020400) = 0.01220961 btc

That assumes you're only sending to 1 address and spending the full amount (ie. no change)... and are willing to wait the 2 weeks for your transaction to confirm

Given the network used to drop unconfirmed transactions in around 72 hours, and your wallet was from 2013 that transaction is long gone

Was the old transaction an incoming or outgoing tx?

If you want the unconfirmed transaction gone and is still in your wallet... you should be able to use the -zapwallettxes commandline option to get it to drop... make sure you take backups etc

The basic formula is: TX Size = (#Inputs * 148) + (#Outputs * 34) + 10

Outputs is easy... basically how many addresses are you sending to? You said 3000... so that part is sorted.

For the inputs, you would need to see how many UTXOs you currently have in your wallet... and figure out the minimum number of UTXOs that you would need to use to get to the required amount you need to send + fee.  Unfortunately, I can't see any API call that would assist with this part... so you'd need to go through your wallet manually to figure it out. For each UTXO you need to use, that equals 1 input. So, if you needed to use say 20 UTXOs to get to the required amount, you'd have 20 inputs.

Then you can just pop those two numbers into mocacinno's fee estimate, Option #2 and click estimate...

and if your wallet did have a password... I have written some python scripts that can extract keys from a MultiBit Classic .wallet file... available with instructions here: https://github.com/HardCorePawn/multibit_recovery

You would need to install Python and a couple of Python libraries... For added security, if you are able to, I'd suggest setting up a Virtual Machine and running the scripts inside the virtual machine with all the network adapters disabled so there is no chance your keys can get leaked.

The scripts have been tested on Windows 10, Linux and MacOSX

Looks like your transaction got confirmed! YAY!

For future reference, if you have an iOS or newer Android device, Breadwallet works with MultiBit HD seeds (tested with 12 on iOS/Android and 18 word seeds on Android)... If you have an older Android device "Simple Bitcoin Wallet" also supports MultiBit HD seeds (tested with 12 and 18 word seeds).

So you can simply restore/recover your wallet with one of those apps if necessary.

Also, it seems like MultiBit HD will keep rebroadcasting transactions and doesn't seem to offer a way to abandon a transaction. So if you want the transaction to drop, you will need to shutdown MultiBit HD and don't open it for a while. For added fun, it would appear that due to the massive number of transactions in the mempool these days, some nodes are waiting much longer than the old "72 hours"... I saw Lauda mention that it could take up to 14 days for transactions to drop

What they say is:

And the link they provided takes you directly to their Service Announcement thread...

Why are you threatening "this place" with a negative review... when it has pretty much ZERO relationship to BitBlender... other than both things being bitcoin related? That's like going to your local bar and complaining at them because you got bad service at the gas station down the road?

Do they not have any advertised support/contact method for the BitBlender service on their website?

Perhaps you should be posting in the BitBlender thread in the "Services" section and see if they respond... the user "blender" was last active on the 14th... so about a week ago.

If no response is received after maybe 24-48 hrs then maybe start a thread in the "Scam accusations" subforum...

So he didn't pay a decent transaction fee at all... it is only 104 sats/byte...

People need to stop looking at the "total" fee and look at the sat/byte fee value... that is pretty much all that matters. A 0.1 BTC fee sounds big, but if your transaction was 75,000 bytes, it only works out to 133 sats/byte Similarly, a 0.00076800 btc fee doesn't look big, but for a 192 byte transaction, that is 400 sats/byte and likely to get confirmed in 1 block.

That transaction is spending from unconfirmed parent transactions. It will not confirm until all the unconfirmed parents are confirmed:

This one in particular is going to screw you... it only has a 3 sat/byte fee, so you won't even be able to use the ViaBTC accelerator.
https://blockchain.info/tx/4812716dc2815a3384b378f455bef8f3484cc13e07a998b5caa25b150ad10dd6

https://blockchain.info/tx/fe66c9a968ee8d51b60d052e504496005fa16b574a23a41b467da4eacc9d93e6
which also has an unconfirmed parent:
https://blockchain.info/tx/6d563596cf691cc26d6585a10e3f89626cc322cd85b2bb9c5dd0ecfe3862e484

Your fee was way too low. The current recommended fees are much higher (and have been for a number of days now):


Goto this link: http://www.mocacinno.com/feecheck.php?txid=572aa54400b82af1c9fa28034736dd6d739cceabe4036fa29fdd0df94e3e5563

It has a number of options available to you for getting your transaction confirmed (both free and paid options)

Additionally, if you are using blockchain.info wallet (guess based on the 120 sat/byte fee)... I would suggest you either stop using it as their so called "dynamic fee" system is broken... or you click the "Advanced Send" button on the "Send" popup box and make make sure the fee is at the correct level to avoid this happening in the future.

Are you sure you're looking at the right thing? That is for address 17S6269gWcmmZcJyJpxno8F5GN2bbvgwjT... but you were previously asking about a May 18th transaction for address: 13YANRDCM4HVtKDUhLYc4zty9gLPLWKx5s

I have found that for some people it helps to think of bitcoin as chunks of gold... your wallet is like a little mini vault, where you store all the chunks that you get.

So say you receive 1 btc, 0.1 btc and 0.01 btc... you now have 3 chunks of gold in your vault worth 1.11 in total.

Now you want to send 0.05 btc to someone. You hand your 0.1 btc chunk to the miners and tell them they can keep 0.0001 btc for their services (miners fee), they break your chunk up, making  a 0.05 chunk that they deliver to the other person, a 0.0001 chunk that they keep for themselves as the fee and then give the remaining chunk of 0.0499 btc back to you as change.

Now, your vault contains 3 chunks, 1 btc, 0.0499 btc and 0.01 btc... worth 1.0599 btc.

It is also possible to take a number of smaller chunks, give them to a miner... and they can "melt it down" producing one bigger chunk (minus their fee of course)...

Hopefully that helps a little...

blockchain.info wallet appears to keep rebroadcasting transactions... not sure if it does it only when you log back in to the wallet, or if it just does it automatically for at set intervals.

Seems you had quite a number of dust sized UTXOs in your wallet... every one of those adds at least 148 bytes (and as much as 180 bytes) to a transaction... even with blockchain.info's retarded low fee of 100 sats/byte, any UTXO that is less than 14,800 sats, actually costs more to send than the transaction is worth... 148 bytes * 100 sats/byte = 14800 sats...

you had:

1EUgShuogtGmh57Q7hzs2dskCnUTptZyRG (0.00002021 BTC - Output)
1MQNbdUrG3e4iNvPfH3pmVw2eKBMup2yt9 (0.00000557 BTC - Output)
1PGWQdzKixdsh4X79fzPCXX1dWwjx2oAXD (0.0000173 BTC - Output)
17T5oYsZD5GcKXNo97ggFqew97LePkSwEV (0.00000571 BTC - Output)

That's 2021 sats, 557 sats, 1730 sats and 571 sats... those 4 inputs make up at least 592 bytes and only total 4879 sats... but would use 59,200 sats to send...   

Without some screenshots of your wallet, it is hard to say for certain what the issue is... but the biggest clue for me is:

It sounds like you might be generating a lot of change addresses with dust amounts of change in them... as explained by DannyHamilton in another thread (which I can't locate right now)... given that fees are currently in the 250-300 sats/byte range... and each input will add at least 148 bytes to a transaction...

Best case (compressed address, lowest "recommended" fee rate):
148 bytes * 250 sats = 37,000 sats per input.

NOTE: If it is an uncompressed address used it could be 180 * 250... = 45,000 sats...

So, if you have UTXOs that are less than 0.00037000 BTC in your wallet... and your wallet calculates dynamic fees... it will probably tell you that you have insufficient funds to send them... as the fee required to send that input is equal to or larger than the input itself

Pretty much the only option is to manually select all the dusty UTXOs from your change addresses... manually set a fixed fee that is calculated to meet the 10 sats/byte (0.00010000 btc/KB) rule for ViaBTC... and consolidate all this dust into one output back into an address that you own. Then attempt to accelerate the transaction using ViaBTC and cross your fingers :-/

Assuming you are using a wallet that actually has CPFP functionality built in... not everyone can or wants to use Electrum.

Looks like they have deleted all their posts today:


Will lock this thread now...

It is all in the timing... seriously, I have about a 99% success rate with ViaBTC submissions by simply putting them in the first few seconds of a new hour. After 2 or 3 minutes, your chances drop to pretty much zero. :-/

Lots of unconfirmed transaction = high demand for free service that helps guarantee confirmations.

It also seems to be spawning scams relating to transaction "acceleration"... so be very wary if you go the pay option.
Wow... was not actually expecting that. All I did was drop the tx into the accelerator But thanks for the tip... Glad you got your tx sorted.

Looks like ViaBTC included it in their latest block... YAY!

Went to add to ViaBTC... transaction is already confirmed... congrats

I just submitted your transaction to the ViaBTC TX Accelerator... fingers crossed it gets a confirmation when they mine their next block.