Stuck transaction on sochain

[Heyui67]

Hi it's transction from roobet

On sochain hash 2576526f091b8a283554c463cc3e6ca77c069eef65854141ed0daecf294279c9

Hours no confirmation.
What can I do to speed it up

[1714972593]

1714972593

[1714972593]

1714972593

[bitmover]

Hi it's transction from roobet

On sochain hash 2576526f091b8a283554c463cc3e6ca77c069eef65854141ed0daecf294279c9

Hours no confirmation.
What can I do to speed it up

I can see it only in sochain. You put a high fee, 223 sat/byte.

https://sochain.com/tx/BTC/2576526f091b8a283554c463cc3e6ca77c069eef65854141ed0daecf294279c9

I could not find your transaction here
https://mempool.space/tx/2576526f091b8a283554c463cc3e6ca77c069eef65854141ed0daecf294279c9

You might need to rebroadcast it, as some nodes are not seeing it.

You can also wait a few hours, as the network is crowded.

[robelneo]

Hi it's transction from roobet

On sochain hash 2576526f091b8a283554c463cc3e6ca77c069eef65854141ed0daecf294279c9

Hours no confirmation.
What can I do to speed it up

I can see it only in sochain. You put a high fee, 223 sat/byte.

https://sochain.com/tx/BTC/2576526f091b8a283554c463cc3e6ca77c069eef65854141ed0daecf294279c9

I could not find your transaction here
https://mempool.space/tx/2576526f091b8a283554c463cc3e6ca77c069eef65854141ed0daecf294279c9

You might need to rebroadcast it, as some nodes are not seeing it.

You can also wait a few hours, as the network is crowded.

The 223 sat/byte  is on low priority so it's not showing on mempool only on sochain you have to bump it based on mempool level of priority

or OP have to wait for the network to
decongest I also have an urgent need to transact but I was charged $20 up from the $1.50 charged from my local exchangers I don't think I'll go for it at the current situation.

[AbuBhakar]

I hope OP is still well since this transaction is still not confirmed until now. I have stuck transaction too from my withdrawal to different casino. The price of Bitcoin drop hard since I withdraw my funds.

@Bitmover, can you help me to understand what happened on this case. Why does his transaction is available on sochain while its not visible on other blockchain explorer like mempool. Is sochain an off-chain explorer by the company? When will it appear on other explorer?

[o_e_l_e_o]

The problem here is actually that the transaction OP has linked is the 26th transaction in a chain of unconfirmed transactions. The maximum number of unconfirmed ancestors or descendants by default is 25. You can see the code for this here: https://github.com/bitcoin/bitcoin/blob/e9262ea32a6e1d364fb7974844fadc36f931f8c6/src/policy/policy.h#L59-L65

Because OP's transaction exceeds this limit, the vast majority of nodes will not accept it until at least the first unconfirmed parent transaction has been confirmed.

There is nothing OP can do here to speed this up. None of the parents are opted in to RBF, and since the chain of transactions has already hit the maximum descendant limit, he cannot use a CPFP since it would also be over the limit and therefore won't be accepted. He just has to wait.

[Cantsay]

~~~

At the time of me writing this post, Op's transaction has received 11confirmations so Op should have his coin in his wallet by now.

It was nice learning new thing from this reply of yours, I never knew that exceeding the limit of unconfirmed ancestors or descendants one has could cause a delay in their transaction no wonder when I search for the transaction hash on mempool yesterday I found nothing there.

[DaveF]

~~~

At the time of me writing this post, Op's transaction has received 11confirmations so Op should have his coin in his wallet by now.

It was nice learning new thing from this reply of yours, I never knew that exceeding the limit of unconfirmed ancestors or descendants one has could cause a delay in their transaction no wonder when I search for the transaction hash on mempool yesterday I found nothing there.

Some people tried to scam by doing that last time the mempool got really full. I don't know if it was successful or not, but there was a discussion about how someone was trying to get someone else to accept a TX that went back to dozens of unconfirmed TXs.

IIRC it was back in the 2017 mempool bloat. Have to see if I can find the discussion. Could have been later then that too.

-Dave