en
Back to the list

Shiba Inu Futures Flow Jumps 1,724% in One Hour as Price Weighs Next Move

source-logo  u.today 2 h
image

Dog-themed cryptocurrency Shiba Inu ($SHIB) has seen a 1,724% jump in futures netflows in the last hour, attracting the market's attention.

According to CoinGlass's one-hour data for spot flows, Shiba Inu reported $144,380 in inflows and $108,020 in outflows, accounting for a positive net inflow of $36,370, with the net change yielding a 1,724% increase.

The Shiba Inu price traded in green after days of dropping, posting gains in Tuesday's session. At press time, Shiba Inu was up 2.31% in the last 24 hours to $0.0000086 but still down 8.06% weekly.

Futures flows measure the capital flow of the futures market. In the Asian session on Tuesday, a burst of buying lifted prices, but broader conviction remained limited as traders waited for clearer catalysts.

Shibarium clarification made

The Shiba Inu community X account highlighted that most connection problems on Shibarium are usually not network related. It added that if something is not working on Shibarium, it is usually a wallet connection issue, not a network issue.

Shibarium $SHIB.io noted that most problems encountered by Shibarium users often come from an outdated or incorrect RPC. It provides a few resolution tips to try in the case of connectivity issues such as clearing wallet cache, and removing the Shibarium network before re-adding it again using the correct RPC. This, it said, might help to resolve the issue quickly.

"Before assuming anything is wrong, please try the following: Clear your wallet cache, remove the Shibarium network , add it again using the correct RPC. In most cases, this resolves the issue immediately," Shibizens wrote.

In a separate tweet, Shibarium $SHIB.io highlighted a Shibarium explorer issue, where some users observed that certain tokens and NFTs were not displaying correctly on Shibarium Scan or within wallet $NFT tabs. Shibarium $SHIB.io says this issue appears to have been related to explorer indexing delays and a temporary bridge update. There was no indication of asset loss at the protocol level.

u.today