Operator-cap: keep to 1–2 presets to avoid silent zero-result returns. More in Settings →
from
over the
in
·
—
each refresh ~240 tweets·~10s
Deeper scans see more of the chatter but take a little longer and cost more razors. Cost scales with the tweets a scan returns — the per-scan estimate in the page header shows the live rate, and every scan posts what it actually spent.
How many per scan
~300 handles / scan · full cycle ~62 scans
TierN/A · list curated
Window
Lang
Pulse not configured. Page renders demo data until scanning is set up — open Settings to configure the proxy URL or API key.
Sample data — these cards show made-up example tweets to preview the layout. They are not real posts. Press Refresh to scan live.
When Source = KOLs, Pulse scans a curated universe of crypto accounts maintained by Razor Alpha. Each scan samples a rotating subset; recently active accounts surface more often. Cache vs Live is the Cache / + Top up / Live control on the toolbar.
0 accounts trackedManaged by Razor Alpha
Coverage (how many accounts per scan) lives on the Depth token in the scan sentence at the top of the page.
Curated by Razor Alpha. The account universe is maintained centrally — adjust coverage and freshness from the scan sentence, and use Source = KOLs to scan it.
$—
—
No data yet — click a ticker on Pulse
Pulse watchlist
Watched terms are pinned in every scan even if they fall below the volume cutoff — they\'ll surface on Heatmap, Velocity, Sentiment, and the per-ticker drill-down. Right-click any cashtag on the Heatmap or Emerging module to add it here.
Custom date range
Times are interpreted in your local timezone. Range must be at least 5 minutes wide and start no more than 30 days in the past — Twitter's archive thins past 7 days on most plans.