Install the Base Radar extension

Install the Base Radar extension to access real-time on-chain data for the Base network. This tool overlays transaction metrics directly onto your browser, enabling immediate visibility into capital flows.

Base Radar
1
Add the Extension
Navigate to your browser’s extension store. Search for "Base Radar" and select the official listing. Click Add to Browser to install. Verify the publisher name matches official documentation to avoid counterfeit extensions.
2
Grant Permissions
Once installed, the extension requests permissions to read page content on supported crypto sites. Review these carefully and click Add Extension to confirm access. This allows the tool to overlay real-time data on DEX interfaces.
3
Verify Installation
Click the Base Radar icon in your toolbar. If the dashboard loads, installation is complete. If you see a blank screen, refresh the page. The extension is now active.
  • Downloaded from official source
  • Permissions granted
  • Dashboard loads correctly

Configure your market dashboard

Base Radar aggregates data across multiple networks. To track real-time crypto movements on Base specifically, isolate the chain from the noise. A cluttered dashboard leads to missed signals.

1
Open dashboard settings
Click the gear icon in the top-right corner of your main dashboard view. This opens the global configuration panel where you can adjust data sources and visualizations.
Base Radar
2
Filter by network
Locate the "Network" or "Chain" filter dropdown. Select "Base" from the list. Unchecking Ethereum or Solana removes irrelevant transaction volume, allowing you to focus strictly on Base chain activity.
3
Enable Base-specific widgets
Scroll to the widget library and toggle on "Base TVL," "Base Gas Tracker," and "Base Active Addresses." These three metrics provide the core health indicators for the network. Remove any widgets related to L2 aggregators unless you are specifically monitoring arbitrage opportunities.
4
Set real-time refresh rate
In the display settings, set the data refresh interval to "Real-time" or "1 second." Base moves quickly; a 5-minute delay can render your entry or exit data obsolete. Verify the timestamp in the top corner updates as transactions occur.

Essential Widgets Checklist

Ensure these core components are active before you begin monitoring:

  • Base TVL (Total Value Locked)
  • Base Gas Tracker
  • Base Active Addresses
  • Real-time Transaction Feed
  • Base DEX Volume

Dashboard Comparison

MetricBase SpecificAll Networks

Live Market Data

Monitor real-time transaction flows

Interpreting live transaction data on Base requires distinguishing between organic retail activity and coordinated whale movements. Base Radar visualizes these flows as they happen, allowing you to spot large capital injections or exits before they impact market price.

Base Radar
1
Identify large wallet clusters
Filter the transaction feed to isolate wallets exceeding a specific ETH threshold. Large, single-txn movements often signal institutional rebalancing or whale accumulation. Look for patterns where multiple wallets from the same cluster execute similar trades within minutes of each other.
2
Track gas price anomalies
Sudden spikes in gas prices often precede high-stakes arbitrage or liquidation events. Monitor the mempool for transactions with significantly higher gas fees than the network average. These "priority" transactions indicate urgent market activity that could shift short-term trends.
Base Radar
3
Correlate with token price action
Overlay the transaction flow data with a technical chart of the target token. If large inflows coincide with a price breakout, the trend is likely supported by genuine demand. Conversely, if price stagnates despite heavy whale buying, it may indicate accumulation before a dump.
4
Verify source of funds
Use blockchain explorers to trace the origin of large incoming transactions. Determine if funds are coming from centralized exchanges (CEX) or decentralized protocols. CEX withdrawals often signal intent to sell or move to cold storage, while DEX swaps may indicate active trading strategies.

Set up alerts for market shifts

Automated alerts turn Base Radar from a passive dashboard into an active risk management tool. Configure the system to notify you only when price action or volume breaks your defined thresholds. This approach preserves capital by removing emotional decision-making.

Configure price and volume triggers

Navigate to the Alerts tab in your Base Radar dashboard. Select the specific crypto asset you are tracking and choose between Price Alerts or Volume Spikes. For high-stakes trading, set alerts slightly outside the current range to avoid false signals from minor wicks.

Base Radar
1
Select the asset
Open the asset list and click the token you want to monitor. Ensure you are on the correct network (e.g., Ethereum or Solana) to avoid tracking the wrong contract address.
Base Radar
2
Define the trigger condition
Choose between a simple price threshold or a percentage change. For volatile assets, use percentage-based alerts (e.g., ±5%) to account for rapid market swings.
Base Radar
3
Set notification preferences
Select your delivery method. Email is reliable for daily summaries, but push notifications or SMS are critical for intraday breaks that require immediate action.

Filter for high-impact signals

Not all alerts are equal. Base Radar allows you to filter alerts by Market Cap and Liquidity. Disable alerts for low-cap tokens with thin order books, as their prices can spike artificially on low volume. Focus your alert budget on top-tier assets where volume confirms the trend. This filtering prevents "alert fatigue," ensuring you only receive notifications for moves that matter to your portfolio.

Common setup errors to avoid

Small configuration mistakes can lead to inaccurate data or missed alerts. When tracking crypto markets in real time, precision matters. A single misconfigured parameter can skew your insights or cause you to miss critical market movements.

Ignoring Data Source Connectivity

The most common error is assuming your data source is connected without verifying the handshake. If the connection is unstable, your radar will show stale data. Always check the connection status indicator in the dashboard. If you see a red warning, re-authenticate your API keys immediately. Do not proceed with analysis until the status is green.

Misconfigured Alert Thresholds

Setting alerts too close to the current price creates noise. You will be bombarded with notifications for minor fluctuations that do not impact your strategy. Conversely, setting them too far away means you miss the entry or exit point. Use the 24-hour volatility range as a baseline. Set your initial thresholds at 1.5 standard deviations from the mean, then adjust based on your risk tolerance.

Incorrect Time Zone Settings

Crypto markets run 24/7, but your local context does not. If your radar is set to UTC but your trading desk operates in EST, you will misinterpret timestamps. This is especially dangerous during high-volatility events like US market opens. Always sync your dashboard time zone to your primary trading location. Double-check this setting after any platform updates.

Overlooking Data Refresh Rates

Not all data feeds update at the same speed. If you are aggregating data from multiple exchanges, ensure you are using the same refresh interval. Mixing real-time WebSocket feeds with delayed REST API calls creates a fragmented view of the market. Stick to a single, high-frequency data source for critical tracking to maintain consistency.

Skipping the Test Trade

Never go live with a new configuration without a test. Use a paper trading account or a small position to verify that your alerts trigger correctly. This step catches syntax errors in your conditions and confirms that your notification channels (email, SMS, or push) are working. It is a small step that prevents costly oversights.

Neglecting Historical Backtesting

Your parameters might look good in theory but fail in practice. Before committing real capital, run your settings against the last 30 days of historical data. This helps you identify if your thresholds are too tight or too loose for current market conditions. Adjust your settings based on these results to improve accuracy.

Forgetting to Update API Keys

API keys expire. If you do not rotate them regularly, your data feed will cut off unexpectedly. Set a calendar reminder to check your key expiration dates every quarter. Most platforms allow you to generate new keys instantly. Update them during low-traffic hours to avoid downtime during active trading sessions.

Frequently asked: what to check next