As cryptocurrencies gain traction, stablecoins like Tether (USDT) have become crucial for traders and investors seeking stability. USDT, pegged to the US dollar, has expanded to blockchain networks like NEAR Protocol. NEAR, known for its high-performance infrastructure, offers a secure environment for decentralized applications (dApps). USDT integration within NEAR enables seamless transfers and brings stability, liquidity, and innovation to the ecosystem. It provides a reliable store of value, enhances accessibility to digital assets, and opens opportunities for developers to build financial dApps. USDT's presence on NEAR reshapes decentralized finance and paves the way for broader adoption.

In this dashboard, I have conducted an analysis of the usage and flows of USDT (Tether) on the NEAR Protocol over the past 30 days. The purpose is to examine how users have interacted with this popular stablecoin within the cryptocurrency ecosystem on the NEAR Protocol.

To begin, I delved into the swapping activity of USDT on the NEAR Protocol. This involved studying the tokens that have interacted with USDT and the behavior of individuals or entities involved in these swaps over the past 30 days. Furthermore, I explored the flow of USDT to other sectors within the NEAR ecosystem, particularly centralized exchanges (CEXs). This analysis aimed to determine whether users have been transferring their funds from the NEAR Chain to CEXs or vice versa.

To perform this analysis, I leveraged the NEAR.core schema provided by Flipsidecrypto. I utilized multiple tables, including ex_dex_swaps, fact_actions_events_function_call, and various dim tables. These tables enabled me to extract relevant labels and token statistics for further analysis.

IMPORTANT: Please note that the timeframe for the analysis is adjustable. While I have focused on the past 30 days, you can modify the timeframe according to your preferences by modifying the value of the Last_Days field at the top of the dashboard. For instance, you can analyze the past 7 days or the past 14 days by updating this parameter.