hi,
thanks for the quick help.
the transaction id is: a4a2f6f82b1fe40732af81f13cc62ea315bfb9eb3d20b0a804cbef9d0e260f45-000
i can´t find anything on blockchain.
i am not sure if it´s safe to post the bitcoin address here.
don't worry the only thing that's not safe to post is your wallet seed and private keys of your addresses. it's safe to post tx ids and address in public.
if i follow the steps shorena posted - should i safe the wallet somewhere before?
yes. always back up your wallet.dat before doing anything to it.
@encrypted how long u guess until the blockchain forgets the transaction?
hours? days? weeks?
that depends. if no one else is rebroadcasting your tx then it should be forgotten in a day or two.
does it make sense to delete the transaction and wait until blockchain forgets it to send a new transfer
yes. that's exactly what you should do.
how long could the transaction without fee take? days? weeks? months?
depends on it's priority and the state of the mempool. shouldn't take more than few weeks if you keep rebroadcasting it.
and also i would like to know if the issue with fees is new!?
i traded some bitcoins 4-5 years ago. i don´t remember fees being an issue back then.
well the issue is not exactly the fee. it's just there's a huge number of unconfirmed transactions waiting in the mempool since yesterday and to get past that quickly you'll need to pay a higher fee.
so i safe my wallet and follow the steps shorena posted;
then i have to wait approximately 24 hours until the blockchain forgets the transcation.
and the bitcoins will appaer in my wallet again?
is this right?
right.
edit:
looks like your tx got dropped already.
edit2:
For one this ^ and the other thing is that with 0.12 there is a certain time after which TX get dropped from mempool and the default 300 MB limit (which is easily hit with the current number of TX). Id have to look it up, but usually you get a pretty high "forgotten" rate after 24 hours, because not all nodes run 24 hours (e.g. most home run nodes are rebooted after that time).
oh yeah. the memory pool limiting. didn't understand how that works until I read this.