Nope. It does not matter if you receive coins on a different address or not. Each time you receive coins its an input you can use later. If you dont combine the inputs in advance (and pay a fee for doing so in a TX) they will increase the size of the TX in byte which increases the fee.
What you can do - maybe - to lower the fees is the to lower the number of inputs. If you get them by withdrawing from services, consider withdrawing less often.
You have many inputs (because you're collecting dust), so transaction fees is very high. So, common address isn't involved much in this case.
So, your transaction size become very big & transaction fees is very high.
Solution, lower your TX fee. But, your transaction will be confirmed longer or won't confirmed.
Judging from the amount of inputs you have, the size of your transaction is huge. Since miners uses fees/kb for their calculation of priority, the fees in total would be higher if the client wants it to be confirmed ASAP. Regarding the 0.0001BTC/kb fees, it can be affected by the network load and if miners would be willing to accept it. If you base it on a service which calculates the fees, it isn't fully accurate if the transaction is not seen by it. I would just put 0.0001BTC/KB or go to
https://www.blocktrail.com/BTC and add the optimal fee in.
Note: If blocks/Blocks with only coinbase transactions are mined regularly, no transaction can be confirmed till the network relays a valid block with transactions other than coinbase is included.
That is around 8 dollar cents per kb. Do you really think that is that high?
It is more than the recommended 10k satoshi though. Maybe just turn of dynamic fees and put it at 10.000 per kb.
Hi all, Thank you very much for the inputs. I think I get it now. :-) I naively believed all the transactions to a common address will be merged/flattened.
Another question: So, it does not matter what wallet I use? Does it help if I were to use only blockchain.info wallet?