stuck tx, looking for viable solution

[rafik35]

So in other words i would have to sum fee that would be used for 3 transactions and divide that sum by total size of 3 tx's in vbyte and conclude if that would push my tx?

I have now 134, 222 and probably 323 vbyte transaction that gives me total sum of 679.
I would use 911, 22000 and around 27000 sats that is 49 911.
That would give me 49911/679 = 73,5 sats/vbyte. Not bad considering were i started.
Am i calculating this right?
The 323 number is taken from first tx that was generated from bitcoin atm, the sender is the same. This time it would be done by human so it might be lower than this.

Just called the guy from atm company and he said he'll do the transfer tomorrow, i'm so pissed.

[rafik35]

So i'm not sure, but i think i managed to screw up my situation again.
I saw on btc.com that my tx is no longer in mempool. So i "ran" to my wallet (before thinking to check other explorers), deleted local tx and broadcasted new one, with 47sats/byte with rbf active in case i need it tomorrow.
Some of the explorers see new transaction (218eaf4dbce7d50e20355c5ae29d5f4cc2a9f4abcb0158044926bf344ceb3878), some of them don't - still see previous one. One of them marked it even as double spend. https://www.smartbit.com.au/tx/87f45f4054eb12c8dcbc7e14ba71cca166ddc270640fdb8a11b5893a0f2ec634
What will happen if electrum catch that first transaction from network again?
Should i worry about it? Or i just have to wait for rest of them to drop old tx and accept new one?

[NotATether]

I saw on btc.com that my tx is no longer in mempool. So i "ran" to my wallet (before thinking to check other explorers), deleted local tx and broadcasted new one, with 47sats/byte with rbf active in case i need it tomorrow.
...
What will happen if electrum catch that first transaction from network again?

You deleted the first transaction from Electrum and that is what matters. It should no longer be related by full nodes or in their mempools. The behavior you are seeing is just the block explorer databases keeping the old transactions cached in their systems, and the ones that are showing the second transaction are giving the correct result.

(By the way, this transaction has since been confirmed so you don't have a problem anymore.)

[o_e_l_e_o]

So in other words i would have to sum fee that would be used for 3 transactions and divide that sum by total size of 3 tx's in vbyte and conclude if that would push my tx?

That is correct. You need to consider your final transaction and every unconfirmed parent (including if those unconfirmed parents have unconfirmed parents, and so on) for your final calculation.

Am i calculating this right?

Provided the sizes and fees you are listed are accurate, then yes, your calculations are correct.

You deleted the first transaction from Electrum and that is what matters. It should no longer be related by full nodes or in their mempools. The behavior you are seeing is just the block explorer databases keeping the old transactions cached in their systems, and the ones that are showing the second transaction are giving the correct result.

This is not necessarily true. Although some nodes dropped his first transaction, and would therefore accept his second one as it wasn't flagged as a double spend, some nodes did keep his first transaction in their mempools, and they are not "incorrect" for doing so.