Bitcoin sent to me but not received? What is this ? Help please

[Scotland]

Hello, on March 21, btc transfer was made to me via blockchain.

I'm using another wallet and btc was shown in my wallet, but it says "WAITING FOR VERIFICATION" so my wallet still hasn't received btc.

When I wrote to the sender , he said that it was sent from me , such an error appears in the txid , what is the problem ? Will this reach my wallet or how long will it take? thanks



TXID

https://www.blockchain.com/btc/tx/11e64f20355e8b4799e9863725680687ad5ea8cabc81f0348fb6aba75b289c25

[1714927330]

1714927330

[1714927330]

1714927330

[1714927330]

1714927330

[OmegaStarScream]

This looks like a double-spend. The funds were sent elsewhere with higher fees:

https://www.blockchain.com/btc/tx/824fc21240b279e6638b1fc6a7c8090dd201180efcd535cf9752dd7a716e3ade

So unless this is your address bc1q7l347h9yp6heax5dsgr7llelnznhz4eyg7uvmp you're not going to receive the funds.

[Pokapoka124]

Yep it's a double spend, the coins were diverted to another address I'm suspecting does not belong to the OP. Appears to be a scam attempt. I have been in a similar situation before. The scammer made two transactions, the first to OP which has invalidated because of the low fee and the other to this address bc1q7l347h9yp6heax5dsgr7llelnznhz4eyg7uvmp with a higher fee, the latter was successful. This is one of the reasons why it is important to always wait for at least 2 confirmations on the Blockchain before payment.

[hosseinimr93]

This looks like a double-spend. The funds were sent elsewhere with higher fees:

The fund hasn't been sent to anywhere else.
In the transaction shared by OP, 0.007 BTC was supposed to be spent from bc1q7l347h9yp6heax5dsgr7llelnznhz4eyg7uvmp.
As seen in the blockchain, there is no outgoing transaction from this address at all and the 0.007 BTC is still in that address.
The transaction in question was invalidated, probably because the parent was invalidated, not because that 0.007 BTC was double-spent.

[Western_Boris]

It now says this:
Transaction invalid: some outputs that it attempts to spend have been already spent or are no longer valid.

[DdmrDdmr]

I’m not sure if I’m seeing it correctly, but looking at the date/time information in the TXs, it looks like the sender tried to send some Sats before he actually got the first confirmation for receiving them, thus invalidating the subsequent TX shown in the OP.

1)   bc1q7l347h9yp6heax5dsgr7llelnznhz4eyg7uvmp received  0.007 BTC and was confirmed on block 728,371, which was mined on Mar 21, 2022 3:20 PM UTC

https://blockchair.com/bitcoin/transaction/824fc21240b279e6638b1fc6a7c8090dd201180efcd535cf9752dd7a716e3ade
https://blockchair.com/bitcoin/block/728371

2)   OPs referenced TX "was first broadcast to the Bitcoin network on March 21, 2022 at 4:09 PM GMT+1" according to the data here (trying to send Sats from bc1q7l347h9yp6heax5dsgr7llelnznhz4eyg7uvmp):

https://www.blockchain.com/btc/tx/11e64f20355e8b4799e9863725680687ad5ea8cabc81f0348fb6aba75b289c25

which is 3:09 PM UTC, and therefore, prior to the first receiving TX’s first conformation (3:20 PM UTC). That is, unless I’m reading the times wrong.

[hosseinimr93]

I’m not sure if I’m seeing it correctly, but looking at the date/time information in the TXs, it looks like the sender tried to send some Sats before he actually got the first confirmation for receiving them, thus invalidating the subsequent TX shown in the OP.

Most probably, the sender abused the RBF feature.
Below are the steps to do so.

1. Send bitcoin from address A to address B and flag the transaction as RBF.
2. Send the fund from address B to address C while the transaction from address A to address B is still unconfirmed.
3. Bump the fee of the transaction made from address A to address B.

Now, the transaction from address A to address B has a new hash. This makes the transaction from address B to address C invalid.

This is why we see that the transaction sending 0.007 from bc1q7l347h... has been made before the transaction sending that fund to it.
In fact, the 0.007 BTC sent from bc1q7l347h... in the transaction shared by OP isn't that 0.007 BTC received in this transaction at all.
That 0.007 BTC had been received in another transaction which is invalid now.

[PX-Z]

Pretty obvious a double spend. There is a status on blockchain explorer status: Invalid, theres also a large red alert message there.

If this is a sell/buy transaction where the sender wants to buy from you and you already give the item to him/her, if this is also a mistake from him try to message and explained it to him that the status is invalid so the btc will never come to you. But if the tx is intentional by the sender, I don't think you can still get this btc from him/her.

[nc50lc]

To support hosseinimr93's reply:
This is the original transaction that had the 0.007BTC output the sender spent on your "not-received" transaction: 2781fa06820f9307291602e409a9276342d48a0dea6d7bbe344ba0b779f7316c
It's replaced by 824fc21240b279e6638b1fc6a7c8090dd201180efcd535cf9752dd7a716e3ade so, your transaction (its child transaction) is invalidated as well.

There's no reason to increase the fee at that time because 1.35sat/B is good enough to be mined in the next block so it must be a scam.
But it wouldn't hurt to ask him if he used "increase fee" or "RBF" to bump the fee because that invalidated the txn he sent to you.

Important note: you must not finish a deal until the transaction has at least 1confirmation.