Only if there was only a any to view who those 500 unconfirmed transactions belong too... that would help my investigation.
You mean the parent transaction with 500 inputs?
All of those inputs are confirmed so the problem is just its size (
33918 vB + its children) which requires a lot of fee to set a good fee rate.
Whoever added CPFP to my transaction knew exactly what they were doing. They even went as far as to adding a Locktime to the transaction so that it didn't get confirmed on the next block, giving them enough time to create a new CPFP transaction.
Don't overthink it; with or without locktime, it wont get confirmed if the parent is still unconfirmed.
Some wallets or services usually uses locktime with the current tip (
block height) of the blockchain.
Also, those CPFP transactions don't look intentional but rather other priority transactions sent to others. (
the sender must be using a custodial service)
It's just the change of the previous transaction was used to send to the next which is the usual.
