How to Check if Your RE Deposit to Binance Hasn't Been Credited
If your RE deposit to Binance hasn't arrived, first look up the TxID on an Ethereum blockchain explorer. If the status is "Success" but your Binance account doesn't show the funds, it's usually because Binance requires a certain number of block confirmations (about 12–20) or the transaction occurred during network congestion. If more than 2 hours pass and the deposit still hasn't appeared, submit a request through 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. Find the TxID of This Transfer on the Sending Platform
What to do: Go back to the platform (wallet or exchange) from which you sent the RE and copy the transaction's TxID (transaction hash).
How:
Case A: Withdrew from another exchange. Log into the sending exchange, go to "Assets" or "Withdrawal History," find the RE transfer record, and copy the TxID. A TxID is a 64-character hexadecimal string starting with 0x.
Case B: Sent from an on-chain wallet. Open your wallet app (e.g., MetaMask, Trust Wallet), locate the transaction record for that transfer, and copy the TxID.
When you're done: You have the TxID for this transaction.
Prerequisite: You can log into the sending platform normally.
Common failure: The transaction hasn't been confirmed on-chain yet. If the sending platform shows "Processing" instead of "Completed," the transaction hasn't been packaged, and the issue isn't with Binance.
2. Check the Transaction Status on an Ethereum Block Explorer
What to do: Use the TxID on Etherscan to verify the real on-chain status of this RE transfer.
How:
RE is an ERC-20 token deployed on the Ethereum mainnet. The official contract address is: 0x526526528f35ac738177003b8773b402b8df8143.
Go to Etherscan (etherscan.io), paste the TxID, and press Enter.
Check the key information:
Status: Must be Success for the on-chain confirmation to be considered successful.
Block Confirmations: Binance typically requires the Ethereum network to reach 12–20 confirmations before crediting the deposit. If the confirmation count is low, it's still in the queue — keep waiting.
To (receiving address): Verify that it matches the RE deposit address you copied from Binance.
Token: Confirm it's RE and that the contract address is correct.
When you're done: You've confirmed on Etherscan that the status is "Success" and the confirmation count exceeds 12.
Prerequisite: You obtained the TxID in Step 1.
Common failure: Confusing ERC-20 RE with another token of the same name. RE is a new token listed by Binance in June 2026; older tokens like Augur (REP) have completely different contract addresses. Without verifying the contract address, you might check the wrong transaction.
3. Check Binance Deposit History and Network Status
What to do: If Etherscan shows "Success" and the confirmation count is sufficient but your Binance account still hasn't received the funds, check your Binance deposit history and network announcements.
How:
In the Binance app, go to [Wallet] – [Deposit History] and see if the deposit record exists.
If it shows "Pending" or "Processing," Binance nodes are waiting for network confirmation — just wait.
If there is no record at all, 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 (ERC-20) network. If it says "Suspended" or "Congested," wait until it resumes.
When you're done: You've confirmed that Binance hasn't proactively suspended RE deposits and that the deposit history contains this transaction (even if the status is "Pending").
Prerequisite: You've confirmed the on-chain transaction succeeded in Step 2.
Common failure: During network congestion, Ethereum gas price fluctuations can cause Binance nodes to process slowly. If the chain has over 50 confirmations but Binance still hasn't credited the deposit after more than 2 hours, 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 (If Still Not Credited)
What to do: If everything above checks out but the deposit hasn't arrived after more than 2 hours, submit a request through Binance's self-service recovery feature.
How:
According to Binance's instructions, submitting a self-service recovery application for an uncredited deposit requires:
The on-chain transaction status must be "Confirmed/Success."
In the Binance Help Center, search for "Deposit not credited" or "Self-service recovery" to find the application entry.
Submit the TxID; the system will automatically fill in details like coin, network, and deposit address.
Confirm the information is correct and submit the application.
Track the processing status under "Application Records."
If the self-service recovery channel doesn't work, contact Binance customer service and provide the following:
Binance account email
Coin name (RE)
Deposit amount
TxID
When you're done: The application has been submitted successfully, and you have a ticket number or application record.
Prerequisite: You've confirmed in Step 3 that the on-chain status is "Success" and the deposit history shows no abnormalities.
Common failure: Typos in the TxID when submitting. Just copy and paste — don't type it manually.
Next Steps:
Now follow this order: get the TxID → check status on Etherscan to confirm "Success" → see if confirmations exceed 12 → look for the record in Binance deposit history. If Etherscan shows "Success" with over 50 confirmations but Binance still hasn't credited the deposit after more than 2 hours, use the self-service recovery channel to submit an application. After submitting, watch for in-app notifications from Binance; processing time depends on the manual review queue.
