The blockchain blocks 0.26 btc from me for more than a year

[hosemary]

To add to LoyceV's reply:

Let's say you have made a transaction from address A to address B and due to the low fee, miners don't include the transaction in the blockchain.
To do CPFP, you should make a new transaction spending the same coin from address B with high fee. (Note that you don't invalidate any transaction here.)

If the fee you paid for the child is high enough, miners will include both transactions (the parent and the child) in the same block simultaneously. That's because miners can't include the child without including the parent.


As mentioned by LoyceV, you didn't do CPFP at all.
You made a transaction spending one of the inputs of the unconfirmed transaction and once that got confirmed, the old transaction got invalidated. After that, you spent the other UTXOs one by one in separate transactions.
Its's worth mentioning with making multiple transactions, you wasted some money on transaction fee. You could spend all those UTXOs in a single transaction.

[nc50lc]

Because your transaction fee is too small, you use your Private key to sign a new transaction with a fee equal to or slightly larger than the current bitcoin fee and push the transaction through an intermediary website such as: https://coinb.in/#broadcast
You can learn more at the above website.

This wont solve anything since the issue isn't about broadcast,
It's the actual process of creating a replacement in Bitcoin Core (if he's the sender) or CPFP (if he's the receiver), specify the steps if you want to help.
And there's no point in using another service to broadcast it, he can use his node.

If at the start, he informed that he's also the sender and using Bitcoin Core, the process would've been as simple as:
1. "sendrawtransaction", then 2. "bumpfee" within Bitcoin Core.

If you still can't solve the problem, I have a way for you to try:

OP replied and with it, he confirmed the assumptions that he created the RBF transaction I saw early. (he mistakenly though it was CPFP)

The issue is already solved.