Get told when large wallets move. Filter by size, chain, token, event type or specific address — then choose how and when you're notified.
The raw feed carries roughly 23,000 events an hour. Filters aren't a nicety here — they're the whole point. Every rule shows you how often it would actually fire before you save it.
Sign in to create alerts
Whale alerts are tied to your account so we know where to send them.
Log inVolumes are measured on real data from the last 24 hours.
What to match
When to notify
How to notify
Run against the last 24 hours of real events.
The same matcher that sends your alerts, run backwards over stored events — so what you see here is exactly what a rule would have sent. Answer “how often does this really happen?” before you commit to being paged for it.
Every filter above is available on the feed endpoint. Same vocabulary, structured output —
including match_reasons, so you can see
which clause fired.
The history search above is the same call with a window and pagination. Pass
rule_id to browse a saved rule instead
of raw filters. The response always carries a
data_window telling you how far the
stored events actually reach.
A webhook channel on any rule POSTs the same JSON to your endpoint
as movements happen. See the docs.