Problem on wallet move from multibit to blockchain.info web wallet

[brizio71]

Hello,

yesterday I have exported the private key of my multibit classic wallet and imported successfully on my blockchain.info wallet, on my original blockchain.info wallet there was an existing  bitcoin address then I move the bitcoin present on moved address to my existing blockchain.info wallet address but the transaction is still not confirmed after more than 16 hours:

https://blockchain.info/en/tx/7a349932e013b4d1a293b9d26912ad8c715264b9fb64b2d686d89ac370d8b182

looking the field Estimated Confirmation Time   is indicate the TRX should be confimed Within 6 Blocks (Medium Priority) ....but the is a note that say:

The transaction fee is low than recommended
This transaction is very large

I have made the transaction with default transaction fee, what happen ?

What I can do in order to confirm or delete this transaction ?

Thanks

Fabrizio

[shorena]

Hello,

yesterday I have exported the private key of my multibit classic wallet and imported successfully on my blockchain.info wallet, on my original blockchain.info wallet there was an existing  bitcoin address then I move the bitcoin present on moved address to my existing blockchain.info wallet address but the transaction is still not confirmed after more than 16 hours:

https://blockchain.info/en/tx/7a349932e013b4d1a293b9d26912ad8c715264b9fb64b2d686d89ac370d8b182

Faucets, eh?

Your TX is 24220 bytes and pays a 10000 satoshi fee. Thats ~0.4 satoshi per byte, while currently 30 satoshi per byte is suggested[1]. Since its a blockchain.info TX, I suggest you wait the 2-3 days the require to get your coins back and create a new one with a proper fee afterwards.

[1] https://bitcoinfees.21.co/

[brizio71]

Hello,

yesterday I have exported the private key of my multibit classic wallet and imported successfully on my blockchain.info wallet, on my original blockchain.info wallet there was an existing  bitcoin address then I move the bitcoin present on moved address to my existing blockchain.info wallet address but the transaction is still not confirmed after more than 16 hours:

https://blockchain.info/en/tx/7a349932e013b4d1a293b9d26912ad8c715264b9fb64b2d686d89ac370d8b182

Faucets, eh?

Your TX is 24220 bytes and pays a 10000 satoshi fee. Thats ~0.4 satoshi per byte, while currently 30 satoshi per byte is suggested[1]. Since its a blockchain.info TX, I suggest you wait the 2-3 days the require to get your coins back and create a new one with a proper fee afterwards.

[1] https://bitcoinfees.21.co/

Thanks !

....why for so small amount this transaction is so large ?

...and then the default blockchain.info wallet have not use the correct fee ?

Thanks
Fabrizio

[shorena]

Hello,

yesterday I have exported the private key of my multibit classic wallet and imported successfully on my blockchain.info wallet, on my original blockchain.info wallet there was an existing  bitcoin address then I move the bitcoin present on moved address to my existing blockchain.info wallet address but the transaction is still not confirmed after more than 16 hours:

https://blockchain.info/en/tx/7a349932e013b4d1a293b9d26912ad8c715264b9fb64b2d686d89ac370d8b182

Faucets, eh?

Your TX is 24220 bytes and pays a 10000 satoshi fee. Thats ~0.4 satoshi per byte, while currently 30 satoshi per byte is suggested[1]. Since its a blockchain.info TX, I suggest you wait the 2-3 days the require to get your coins back and create a new one with a proper fee afterwards.

[1] https://bitcoinfees.21.co/

Thanks !

....why for so small amount this transaction is so large ?

Because it uses many low value inputs, look here[1] on the left side.

[1] https://blockchain.info/en/tx/7a349932e013b4d1a293b9d26912ad8c715264b9fb64b2d686d89ac370d8b182?show_adv=true

...and then the default blockchain.info wallet have not use the correct fee ?

Thanks
Fabrizio

A flat fee makes no longer sense, but 10000 is usually fine if your TX is ~250-300 byte in size. If the wallet you use does not allow for a fee estimate you should check with cointape before creating a transaction and estimate its size (in byte) if possible.