How to Troubleshoot ENA Transfers Not Arriving in Binance
If your ENA deposit to Binance is not credited to your account, first use the TxID to check the transaction status on Etherscan. If the chain shows the transaction is marked as Success but it does not appear in your Binance account, this is usually because you need to wait for 12-20 Ethereum network block confirmations, or the transaction was submitted during a network congestion period. If it still does not arrive after more than 2 hours, submit an application via Binance's self-service recovery channel.
The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!
1. Locate the TxID of this transfer from the sending platform
What to do: Go back to the platform (wallet or exchange) you sent ENA from, copy the TxID (transaction hash) of this transfer. This is a required credential for checking on-chain status and contacting customer support.
How to do:
Case A: Withdraw from another exchange. Log in to the withdrawal platform, go to the withdrawal history, find the ENA transfer entry, and copy the TxID. A TxID is a 64-character hexadecimal string starting with 0x.
Case B: Transfer from an on-chain wallet. Open your wallet App (such as MetaMask, Trust Wallet), find the transaction record for this transfer, and copy the TxID.
ENA is the governance token of the Ethena protocol, deployed on the Ethereum mainnet. If your ENA comes from staking or airdrops on the Ethena protocol, you can get the TxID after confirming the transaction status is "Completed".
What counts as completion: You have successfully obtained the TxID of this transaction.
Prerequisite: You can log in to the sending platform normally.
Common failure reasons: You try to check the status before the transaction is confirmed on-chain. If the sending platform shows "Processing" instead of "Completed", it means the transaction has not been packaged on the chain, which is not a Binance-side issue, you just need to wait patiently.
2. Check transaction status on Ethereum block explorer
What to do: Use the TxID to check the real on-chain status of the ENA transfer on Etherscan. ENA is an ERC-20 token deployed on Ethereum mainnet.
How to do:
Open Etherscan (etherscan.io), paste the TxID, and press enter.
Check the key information:
Status: It must show Success to be considered a successful on-chain confirmation.
Block Confirmations: Binance usually requires 12-20 confirmations on the Ethereum network before crediting deposits. If the number of confirmations is very low, the transaction is still queued, just keep waiting.
To (recipient address): Verify that it matches the ENA deposit address you copied from Binance.
Token: Confirm the token is ENA. The official ENA contract address is
0x57e114B691Db790C35207b2e685D4A43181e6061, please cross-check this address when making transfers.
What counts as completion: You confirm on Etherscan that the status is "Success" and the number of confirmations has exceeded 12.
Prerequisite: You have obtained the TxID in Step 1.
Common failure reasons: Mistakenly check ENA as a token deployed on BSC or Solana. ENA is an ERC-20 token, and can only be queried on Etherscan.
3. Check Binance deposit history and network status
What to do: If Etherscan shows Success and the number of confirmations is sufficient, but the ENA is still not in your Binance account, check Binance's deposit records and network announcements.
How to do:
On the Binance App, go to [Wallets] - [Deposit History] to check if there is a corresponding deposit record.
If it shows "Pending Confirmation" or "Processing", it means Binance's node is still waiting for network confirmation, just continue to wait.
If there is no corresponding record at all, it means Binance may be delaying processing due to network congestion or other reasons.
Visit Binance's "Deposit & Withdrawal Status" page to check the current status of the Ethereum (ERC20) network. If it shows "Suspended" or "Congested", wait for service to resume.
What counts as completion: You confirm that Binance has not actively suspended ENA deposits, and the corresponding deposit entry exists in your deposit history (even if the status is "Pending Confirmation").
Prerequisite: You have confirmed the on-chain transaction is successful in Step 2.
Common failure reasons: During network congestion, fluctuations in Ethereum Gas prices may cause slow processing on Binance's nodes. If the number of on-chain confirmations has exceeded 50 but your ENA still has not arrived after more than 2 hours, you need to contact customer support.
The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!
4. Use Binance's self-service recovery channel (if funds still do not arrive)
What to do: If all the above steps are verified correct, but the deposit still does not arrive after more than 2 hours, submit a request via Binance's self-service recovery feature.
How to do:
According to Binance Help Center guidelines, the following conditions must be met to submit a self-service deposit not received recovery request:
The on-chain transaction status must be "Confirmed / Successful".
Search for "Deposit not received" or "Self-service recovery" in Binance Help Center to find the application entry.
Paste the TxID, the system will automatically fill in information such as token name, network type, and deposit address (if the system has a matching record).
Confirm all information is correct and submit the request.
Check the processing status in "Application Records".
If the self-service recovery channel cannot process your request, contact Binance human customer support and provide the following information:
Your Binance account email
Token name (ENA)
Exact deposit amount
TxID
What counts as completion: You have successfully submitted the application and obtained the ticket number or application record.
Prerequisite: You have confirmed the on-chain status is Success in Step 3.
Common failure reasons: Entering the wrong TxID when submitting. Copy and paste directly to avoid errors, do not type it manually.
Next steps to follow:
Operate in the following order: Obtain the TxID → Check status on Etherscan to confirm it is Success → Verify that the number of confirmations has exceeded 12 → Check Binance deposit history for the corresponding entry. If Etherscan shows Success, the number of confirmations has exceeded 50, and your ENA still does not arrive in Binance after more than 2 hours, submit an application via the self-service recovery channel. After submission, pay attention to Binance's in-app notification, the processing time depends on the manual review queue.
