# Why won't a transaction with 888/byte confirm after 11+ hours?

I have this transaction that I can't figure out why it won't confirm.

https://blockchain.info/tx/92b33d498a35d47f03eee14f258cf9b3f015a5d12856eb05e47534e664344239

If I check https://bitcoinfees.earn.com/#delay it says with that it should confirm very quickly.

Thanks.

It won't confirm because the grandparent and parent of your child transaction aren't confirmed. The grandparent transaction was also paid with a really low fee(51.573 sat/B).

I did the math for you.

```Grandparent + parent + child = total transaction size:
3878 Bytes + 226 Bytes + 225 Bytes = 4329 Bytes

200000 Sat + 200000 Sat + 200000 Sat  = 600000 sat

Divide total paid fees with total transaction size:
600000 / 4329 = 138.6 Sat/B

Subtract to find difference needed:
450 Sat/B - 138.6 Sat/B = 311.4 missing Sat/B

```

To sum it up.
On average, the three transactions were paid with a fee of 138.6 Sat/B each.
The fee needed to confirm within 6 blocks is presumably around 450 Sat/B right now.
So the three transactions are short 311.4 Sat/B to reach the target of 450 Sat/B.

• Probably Rob can use reaplace-by-fee in this case to make it faster. Dec 30, 2017 at 16:26
• How can I do that? I used blockchain.info api to make the transaction
– Rob
Dec 30, 2017 at 16:49
• where can I see the parent / gradnparent - transactions on blockchain.info? Dec 30, 2017 at 17:19
• @Rob You can't on most exchanges, however your fee of 138.6 Sat/B will confirm within 48-144 blocks...seems like it just got confirmed now.
– Chak
Dec 30, 2017 at 20:44
• @Alpha just follow the trails where the unconfirmed outputs originate from.
– Chak
Dec 30, 2017 at 20:45