Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transaction Details Not Found #104

Closed
sdefi opened this issue Oct 13, 2020 · 5 comments
Closed

Transaction Details Not Found #104

sdefi opened this issue Oct 13, 2020 · 5 comments

Comments

@sdefi
Copy link

sdefi commented Oct 13, 2020

I created a test on mainnet wallet to send 1 avax which worked

I copied new wallet address to send some more tokens and the tx failed or is stuck.

txid: RngE3Ue9rANeJ6ob32Li11kN7eRwo6S8EA5obJYLzSTiYhr3Z

https://explorer.avax.network/tx/RngE3Ue9rANeJ6ob32Li11kN7eRwo6S8EA5obJYLzSTiYhr3Z

@tasinco
Copy link
Contributor

tasinco commented Oct 13, 2020

What do you mean the tx is failed or stuck? Is this from: https://docs.avax.network/v1.0/en/api/avm/#avmgettxstatus

@sdefi
Copy link
Author

sdefi commented Oct 13, 2020

I withdrew a single AVAX from okex. The single avax arrived, then I tried to send the rest and the transaction was completed at okex end but when I clicked the tx link (as above) that's the error I get. Tokens still have not arrived. I had a chat to okex they said they've sent the tokens but the issue is at avalanche end.

Then when I clicked the (submit issue) from the link above it brought me here.

@tasinco
Copy link
Contributor

tasinco commented Oct 13, 2020

'and the transaction was completed at okex end'

If the transaction was completed, then it would of transmitted onto the network, and all nodes would be updated.

There is no record of txid: RngE3Ue9rANeJ6ob32Li11kN7eRwo6S8EA5obJYLzSTiYhr3Z on explorer, which means it did not actually complete.

The status of RngE3Ue9rANeJ6ob32Li11kN7eRwo6S8EA5obJYLzSTiYhr3Z needs to be checked on the node that sent the Tx. If the Tx is in the state of Processing, it did not actually complete. If you re-submit the Tx bytes you should get notified of the reason it didn't actually Process.

@tasinco
Copy link
Contributor

tasinco commented Oct 13, 2020

after speaking with OKEX the problem looks resolved. The txid: RngE3Ue9rANeJ6ob32Li11kN7eRwo6S8EA5obJYLzSTiYhr3Z is now visible in the explorer.

@tasinco tasinco closed this as completed Oct 13, 2020
@sdefi
Copy link
Author

sdefi commented Oct 13, 2020

Thanks for assisting promptly. The issue was at okex end.

I would suggest diverting the user to another support page instead of github in future. Some issues do not need to be public.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants