Quote from: chantatic on Today at 01:22:19 AM

I found the hash that is holding my transaction hostage.
https://mempool.space/tx/03bda0d33efb2da41c117c139279c1811d297637468c404d487c1d678e974b02#vout=0
It has 499 unconfirmed inputs!!

Quote from: chantatic on Today at 03:25:19 AM

I don’t understand why the sender would be sending me unspent unconfirmed btc, that defeats the purpose of have a payment sent to me with high priority.

It must be automated if it's also from an exchange or custodial wallet.

The large parent transaction was broadcasted 2 months ago (according to mempool.space) when the average fee rate is lower than 10sat/vB,
it's a pattern of a consolidation transaction of an exchange or custodial wallet that even used a medium priority fee at that time.
But they didn't expected the sudden surge in transaction fee and unfortunately, they didn't took action to bump/accelerate it before the fees reach to what it is now.

Quote from: chantatic on Today at 03:25:19 AM

I guess the only solution is to wait till the effective fee rate gets to -17sat/b, as I doubt it will ever get purged from mempool.

For the record, since the first parent transaction is beyond the bottom of the default mempool size, all of its children transaction including it should be dropped from majority of mempools.
I can't find your transaction in my node as well.

However, given that it's still included in some blockexplorers and nodes with high mempool size setting, it will still propagate in the right conditions.
So yeah, there's no cheaper solution but to wait.