Can this transaction be sped up?

Check out this transaction link: https://mempool.space/tx/3a88b7e9edb449562f6a62e05e763d3890b7ffb52b5e8d0c21a19a2f1b2bd042 Are those transaction accelerators for real, or just a bunch of scams? I'm new to this crypto stuff, so any insights would help.

There is one legit accelerator that will actually confirm your tx and not just rebroadcast, and that it is ViaBTC! But on a simulation for your tx they ask for $130 so, looking at your $190 worth of BTC tx, I doubt it is worth it. So, the usual question,are you in control of any of those wallets, or are they custodial wallets? Once we know how that looks we can think of what other options you have, that is if you have any!

Unfortunately im not and someone else said nothing can really be done because it is only a segwit transaction so al i can really do is wait idk how true that is either. Im the receiver but it is on my cashapp wallet

Since it is cash app you are receiving into them from your end you cannot do anything because it is not a non-custodian wallet that allows transaction bumping. The only way is if the transaction is not from an exchange and the wallet of the sender can actually bump the transaction you can simply ask him to or better still double spend your the transaction again from there but if it is an exchange sorry nothing can be done, you may have too wait and hope they don’t continue to rebroadcast the transaction with such low fees. That is not true, you cannot do anything because you’re using a wallet that doesn’t support any bitcoin bumping feature, it is not because you’re using segwit address or receiving on legacy address that is the problem. But the sending and receiving wallet are the problem. In the future try to use a wallet that supports bitcoin bumping to avoid cases like this.

So whats the maximum amount of time it could possibly sit there before it gets sent back or is confirmed or is that not really a thing that can be predicted ?

If the sender keeps broadcasting the transaction, there is no maximum amount of time.

Ideally it is 14 days by default but there some conditions that could still keep it there more than that time. One is if the wallet or sender doesn’t continually rebroadcast the transaction, but if they do then it will certainly take more time. Secondly is since node’s mempools receives transaction in different Time it will also take different Time to drop it and also the size of the pools are different and as such some will keep it beyond that time

The purging fee rate now is at 7.86 sat/vbyte. The transaction is 3 weeks old. If the sender is not using the wallet that keeps on rebroadcasting transaction, he ought to have been able to rebroadcast the coin. Secondly, the purging fee rate is more than the fee rate used to broadcast the transaction, which also means that the sender would have been able to rebroadcast the coin. If the sender import his seed phrase or private on wallet like Electrum, he would have been able to rebroadcast the coin. The transaction also has change (UTXO sent to the change address), he can use coin control to spend the change using high fee that is enough to confirm two transactions. (he fee for the new transaction and the one that will be added to the old transaction in a way that two transactions can be confirmed at once). This has nothing to do with the address type used. It is worth knowing that segwit is better in making low fee transaction. Supposing you used legacy address, you will not be able to save fee. Segwit is also cheaper than nested segwit.

I believe the transaction can be rebroadcast indefinitely, and it may never get confirmed. Contact the sender and asking if they can bump-up the fee. If that's not an option, there's not much else you can do, especially if you don't have control over the recipient's wallet. There are services that can include the transaction in their mining pool, regardless of the fee, but it usually comes at a significant cost.

Every node which is connected to the network will receive the transaction within, at most, a minute or two of each other, so this will make no difference to OP. As Charles-Tim has pointed out, the transaction is already older than the default expiry time, and pays a fee lower than the default purge limit. All default nodes will have dropped it already. And yet, we can still see it on almost any block explorer that you check. There are more and more nodes running with much larger limits than the default, so you can no longer rely on transactions being dropped at all. Instead, given that full RBF is now commonplace, the sender of this transaction could easily replace it with a higher fee paying transaction, even though it is not opted in to RBF. The legacy output address belongs to the exchange CoinSpot, so I assume they are the ones who sent the transaction. The only thing OP can do is contact them and request they replace the transaction.

I suppose blockexplorers connect to more nodes than any other default node or they run their own nodes with increased limits. This is why they will likely show you transactions as unconfirmed even if they've been dropped from the majority of the nodes. I imported OP's address into Electrum (watch-only) and tryed different servers (about 10 servers). Only one of them has the transaction in its mempool and showed the transaction as unconfirmed. The status changed to local when connecting to other servers.

So will it be dropped soon from every mempool most likely? I tries contacting that website and they said nothing they can do i can ask op sender but other than that nothing they could do. I looked at binance for one and they offered a service but at about 80$ i just don’t know anything about accelerators and if they would actually guarantee it to be processed

They may run more than one nodes but increasing the limit of just one node is enough, I think. Supposing you are able to do what we have explained above, you would have been able to either pump the fee or rebroadcast the input, but you are neither the sender nor have the private key of the wallet the transaction was broadcasted from. Before a transaction can be rebroadcasted, it would have been dropped from some nodes mempool. Paid accelerators are expensive and not worth it.

It ideally should have been dropped from majority mempool but hasn't been, so you should not be banking on that anymore. Try contacting both the sender and receiver to know what can be done about the transaction. They are custodial services, and you cannot do anything except they try to fix it. Next time edit your new reply into the first one and don't post consecutively. I will not advice you try paid accelerators.

I contacted everyone i could on wallets so hopefully it just drops or something one day i guess thanks for all the input appreciate it greatly. If it doesnt drop does it stay there forever or something just sitting there as a transaction in the void type of thing?

For next time: use your own wallet to receive Bitcoin. I don't know "cash app", but if it doesn't give you access to the private keys, I wouldn't call it a wallet. The downside of using your own wallet is having to pay transaction fees, but the upside is the possibility to use CPFP when the sender uses a low fee. It'll cost you, but at least you can access your money.

The number of legit transaction accelerators is more than one. Binance offers transaction acceleration service to VIP users and regular users via Telegram. At the moment, it costs 0.002776 BTC to accelerate his transaction but I speculate those who have high VIP rank on Binance like VIP 5 or higher, it might be cheaper for them to accelerate it. Good, they will definitely 100% include your transaction in next block if you pay. By the way, maybe ask if there are some Binance VIP users who can check your transaction on this page https://pool.binance.com/en/acceleration because I think there is a chance, they may do it with discount for high VIP users. Or if $80 is okay for you and don't mind, then contact them via telegram @BinancePoolAccelerator

Connecting to more nodes wouldn't make a difference in the case where the transaction was above the default purge limit when it was broadcast, only if you now tried to broadcast a transaction below the default purge limit. If you only broadcast to nodes which won't relay your transaction, then the nodes with the higher limits will never learn of it. Who is the original sender? Someone somewhere has the ability to replace this transaction with one paying a decent fee. Who is that person? Either you wait until the fee rate drops enough that it will be confirmed, or whoever sent you that transaction will use those inputs in another transaction and invalidate your transaction meaning you will never receive your money.

Will it eventually say declined or something on the mempool? Or what exactly am I waiting to see if it is stuck and never gets confirmed?

the fee was 6.85 sats a byte. So viabtc will not accelerate it for free. https://www.viabtc.com/tools/txaccelerator