Bitcoin Forum

Alternate cryptocurrencies => Service Discussion (Altcoins) => Topic started by: omerchip on February 27, 2021, 11:43:51 AM



Title: Sorry we're unable to locate this TxnHash
Post by: omerchip on February 27, 2021, 11:43:51 AM
 Why im getting that when i put my tx hash code to the ethscsn.
 
I have probem days. Help me please
 
Here is my last transaction attempt

Transaction

(Processing)

2:37:46 PM

2/27/2021

Amount:

6983.957020304203317454 DADI

To Address:

0x5A308089db8A7544938642809449e68b6f10bFC8

Via Contract:

0xfb2f26f266fb2805a387230f2aa0a331b4d96fba

Max Transaction Fee:

0.0067743 ETH ($10.08)

Transaction Hash:

0x9f623b9629f2792813b2d75c973756bb970092d2c11dedd1a413c01e9f9360e0


Title: Re: Sorry we're unable to locate this TxnHash
Post by: omerchip on February 27, 2021, 11:44:48 AM
 
And all the time this error massage

Transaction was not mined within 50 blocks, please make sure your transaction was properly sent. Be aware that it might still be mined!


Title: Re: Sorry we're unable to locate this TxnHash
Post by: Stalker22 on February 27, 2021, 12:43:33 PM
Why im getting that when i put my tx hash code to the ethscsn.
 
I have probem days. Help me please
<cut>

From Etherscan: "When the network is busy it can take a while for your transaction to propagate through the network and for us to index it."

Are you sure you put enough gas price for the transaction?


Title: Re: Sorry we're unable to locate this TxnHash
Post by: omerchip on February 27, 2021, 12:49:49 PM
Why im getting that when i put my tx hash code to the ethscsn.
 
I have probem days. Help me please
<cut>

From Etherscan: "When the network is busy it can take a while for your transaction to propagate through the network and for us to index it."

Are you sure you put enough gas price for the transaction?
Sorry, We are unable to locate this TxnHash

Yes i put enough gas its never under 100 gwei. Hash code i shared but even when click on it it says ' Sorry, We are unable to locate this TxnHash '


Title: Re: Sorry we're unable to locate this TxnHash
Post by: omerchip on February 27, 2021, 03:05:26 PM
you can read this discussion many have the same problem old to 2017/2018 and some solve it with change gas limit.

Quote
Turned out that the gas limit was way too low

https://github.com/ChainSafe/web3.js/issues/1102

it is gas limit problem use any altcoin or wait some time when gas fees down

I read it all and my problem is different i want even see my transaction on ethscan qhen i put my transaction hash id


Title: Re: Sorry we're unable to locate this TxnHash
Post by: nakamura12 on February 27, 2021, 03:07:36 PM
It's either the gas is not enough or the network is busy. It is also the same as the bitcoin where I read a thread that the transaction is not confirmed due to low fee. Try to check your wallet address in the etherscan if you can see a transaction that has not been processed when you send the transaction.


Title: Re: Sorry we're unable to locate this TxnHash
Post by: omerchip on February 27, 2021, 03:19:16 PM
It's either the gas is not enough or the network is busy. It is also the same as the bitcoin where I read a thread that the transaction is not confirmed due to low fee. Try to check your wallet address in the etherscan if you can see a transaction that has not been processed when you send the transaction.

Those all transactions are not seen on ethscan but i reset my metamask and create another transaction and it fixed the problem


Title: Re: Sorry we're unable to locate this TxnHash
Post by: Myleschetty on February 27, 2021, 09:09:10 PM
It's either the gas is not enough or the network is busy. It is also the same as the bitcoin where I read a thread that the transaction is not confirmed due to low fee. Try to check your wallet address in the etherscan if you can see a transaction that has not been processed when you send the transaction.
The problem does not have to do with the gas and it also not the as Bitcoin network congestion but I believe it either the problem is from the OP when he sent the transaction which possibly makes the transaction, not to reach the mempool and that's the reason why the Etherscan cannot present the transaction information cause it is not available on the mempool.