looks like people are paying a higher fee now. this is good (IMO).
many third party services are still paying a fixed fee of .0001 or .0002 for every transaction though. and their tx usually have multiple inputs.

anyone can rebroadcast your tx but if you say stop then they should stop (I think I may have been the one who rebroadcasted the first tx.. not sure but sorry anyway.). just wait more days until the mempool drops the tx again.

that tx spends an input from this tx which is still unconfirmed. you'll need to wait for the first tx to confirm before the second one does.

the first tx have very low fee so it probably will take a long time to confirm. that is if someone keeps re-broadcasting it.

edit:
oh they're gone.

blockchain.info still have it but some other explorers rejected it (some still have the tx.).
it can still be confirmed as long as there's someone rebroadcasting it.

well yeah that's because he spent the change from the first tx. the second tx you posted will not be confirmed before the first.

don't know how long it will take. but it was sent about 3 days ago so it shouldn't take too long (no promises).
I'll broadcast it every 30 minutes or so. you can do it too, read my post here.

EDIT:
ARGH some explorer rejected it. transaction was rejected by network rules (66: mempool min fee not met).  

this is your 3rd thread about unconfirmed transaction... didn't you learn anything from the previous threads?

well ok. you did pay the fee for the second transaction. but that tx spends an input from the first transaction which is still unconfirmed and have no fee.

edit:
oh, there's another tx in between the txes that was posted. that tx have fees just like the second tx.

https://blockchain.info/tx/08b6dbcd4bbfb83320403776e5361044b3d9b02268094585d8381483d666c8ca?format=hex
note the "?format=hex". for core 0.12 just right click on the transaction. no idea how to do that on older version and other wallets.

by the way that part about blockchain showing the tx as high priority just because of the high fee are bull. the priority calculation doesn't have the fee on it.

.00062000 ~ .00077500 (40~50 satoshi per byte). or 1mbtc if you want to be sure. but 20~30 satoshi per byte shouldn't take more than 10 blocks.

that's basically the long version of your tx. you can broadcast them using this method to these sites (or just from your wallet. core does this automatically for unconfirmed transactions.).

fee of .0002 or whatever is actually kind of vague without knowing the transaction size. for all we know he sent a 225 byte tx and/or have over 57,600,000 priority. if his tx meets one of these criteria then it shouldn't take very long to confirm.

no I'm not seeing them. I haven't seen anyone complaining about their 50spb fee tx not going through. and I can't find any either. there's a thread about that FUD article here if you're interested.
(if you're going to reply to this post, reply there. I quoted my post on the first page.)

you can post the tx here so that we can help you rebroadcast it if you can't afford to let the mempool drop the tx and returns the btc to the sender.


I must've missed it or you edited your post. either way here's the raw for that.

raw tx edited out. don't like seeing that long thing on my latest posts. it's quoted below.

tch.


whoever wrote that thing have no proof to back their statement.

EDIT:
well I've read it again and more thoroughly this time and looks like they are exaggerating the normal fee. it was .0001 and not 0.001

if your english is not very good, please ask these kinds of questions in the local board of your country to avoid all kinds of confusion... I'm sure they will be more helpful.

that's a ridiculously high fee for ordinary transaction with normal size. 50 satoshi per byte or around 0.0005BTC per KB should be enough to get all transaction below 1KB confirmed very fast. 20~ spb is good enough.

what a load of bullshit. just a stupid extortioner who spouts everything without giving a slight proof that they know something.

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.

yes. always back up your wallet.dat before doing anything to it.

that depends. if no one else is rebroadcasting your tx then it should be forgotten in a day or two.

yes. that's exactly what you should do.

depends on it's priority and the state of the mempool. shouldn't take more than few weeks if you keep rebroadcasting it.

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.

---

right.

edit:
looks like your tx got dropped already.

edit2:

---

oh yeah. the memory pool limiting. didn't understand how that works until I read this.

core automatically rebroadcast existing unconfirmed transactions every 30 minutes or so. that means the network will not be able to forget the tx because core keep reminding nodes about the tx. so you'll need to close core until the tx gets dropped or remove the unconfirmed transactions from the client.