Main point:
Ether (EthThe range has been linked for several days, but the institutional investor’s request is captured. Glassnode data appears 106,000 Al -Atheer flows In the boxes circulating in the eternal exchange last week, the seventh consecutive week of positive flows.
but, Not everyone is optimistic about the ether. ETHERSCAN displays two unstable ETHEREUMs and withdrew 95,920 ether in June. A large part of it, 62,289 ether, was deposited in many exchanges, likely to be sold.
Will ETHER work to go to the bullish side or the negative side? Let’s study the plans to find out.
Predicting the price of ether
The ether is trading between the simple moving average for 50 days (SMA) ($ 2,528) and horizontal support at $ 2,323 in the past few days.
Each of the moving averages has been settled, and the RSI is near the center point, indicating monotheism in the near term. If buyers pay the price over SMA for 50 days, the ETH/USDT pair may rise to $ 2738 and then to $ 2,879. Sellers are expected to defend $ 2,879.
Instead, if the price decreases from SMA for 50 days, the bears will try to withdraw the husband without supporting $ 2,323. If they can do this, the husband may drown in strong support at $ 2,111. The next ongoing step can start over $ 2,879 or less than $ 2,111.
Related to: Bitcoin dealers adopt a “defensive position” as the ends of ETF flow for 15 days
The husband was stuck between $ 2,376 and $ 2,521 for some time. The consistent moving averages and RSI not give the center point a clear advantage either to bulls or bears.
If the price exceeds the moving averages, the husband may reach a level of $ 2,521. The sellers will try to stop the height at $ 2521, but if the bulls prevail, the husband may rise to $ 2666.
On the contrary, if the price decreases sharply from $ 2521, the husband may extend his stay in the range for a longer period.
This article does not contain investment advice or recommendations. Each step includes investment and risk trading, and readers must conduct their own research when making a decision.
publish_date
