Blockchain wallet "estimated confirmation time unknown"

[mycketbra]

Hi everybody,

A payment was sent to me at 1:30 EST today from a blockchain.info wallet. Blockchain.info confirms that the transaction was sent: https://blockchain.info/tx/25de6b65f77fcd27668c80e4e3ad20c97ed0c0adbea2b22d6d5f3b2122ed7e58

But it says the estimated confirmation time is unknown. Further, the address I received it with is a bitcoin-qt wallet; it hasn't even showed up on my client.

What could be the issue here?

[mycketbra]

Please guys, is it possible that the transaction simply hasn't been included in a block yet since blockchain.info didn't ask for a fee?

[whiskers75]

It probably hasn't broadcasted yet, your client was not open when it did, or you didn't add a fee.
Patience will solve your problem .

[🏰 TradeFortress 🏰]

It probably hasn't broadcasted yet, your client was not open when it did, or you didn't add a fee.
Patience will solve your problem .

The fee is too low.

Are you sure it wasn't custom send and the sender set the fee to 0? I know some people who used to do that..

EDIT: The size is over 1000 bytes (it is 1338 bytes). As there is no fee, this transaction most likely won't confirm anytime in the near future.

[mycketbra]

It probably hasn't broadcasted yet, your client was not open when it did, or you didn't add a fee.
Patience will solve your problem .

The fee is too low.

Are you sure it wasn't custom send and the sender set the fee to 0? I know some people who used to do that..

EDIT: The size is over 1000 bytes (it is 1338 bytes). As there is no fee, this transaction most likely won't confirm anytime in the near future.

Thanks for the replies, I've been trying to get estimates on how long it will take haha. Isn't there a network bounce back eventually?

Luckily if it bounces back, the blockchain.info wallet should accept it. It was strange that it didn't ask for a fee though

[🏰 TradeFortress 🏰]

There is no network bounceback. You will have to double spend it. (Double spending is not always evil). I believe Blockchain.info let's you double spend it after 24 hours.

The sending party may choose to craft a double spend transaction right now and the network should accept it (with a proper fee), as it shouldn't be in any node's memory pool.

[Abdussamad]

The link to the transaction is show not found.

[mycketbra]

There is no network bounceback. You will have to double spend it. (Double spending is not always evil). I believe Blockchain.info let's you double spend it after 24 hours.

The sending party may choose to craft a double spend transaction right now and the network should accept it (with a proper fee), as it shouldn't be in any node's memory pool.

The link to the transaction is show not found.

Hi again, as Abdussamad has noted the transaction is over 24 years old and is no longer on the network. I should safely assume that the balance has returned to the person's blockchain.info wallet and that we can try again with a proper fee?

[DannyHamilton]

There is no network bounceback. You will have to double spend it. (Double spending is not always evil). I believe Blockchain.info let's you double spend it after 24 hours.

The sending party may choose to craft a double spend transaction right now and the network should accept it (with a proper fee), as it shouldn't be in any node's memory pool.

The link to the transaction is show not found.

Hi again, as Abdussamad has noted the transaction is over 24 years old and is no longer on the network. I should safely assume that the balance has returned to the person's blockchain.info wallet and that we can try again with a proper fee?

Check with the sender, but yes, once the transaction is no longer on the network, blockchain.info typically shows the balance back in the senders wallet.

[Guybrush01]

Hi again, as Abdussamad has noted the transaction is over 24 years old and is no longer on the network. I should safely assume that the balance has returned to the person's blockchain.info wallet and that we can try again with a proper fee?

Um, sorry to hijack an old thread, but did you really mean 24 years old?