Ethereum Stablecoin Whale Tracker — USDT & USDC

Find large finalized Ethereum USDT and USDC transfers, filter them by amount or wallet, and export transaction evidence with wallet inflow/outflow summaries and explicit search coverage.

Release status: privately deployed and tested with live Ethereum USDT/USDC events, including explorer comparisons. Not published. Public release is pending; the Pricing tab shows the effective private-run prices. API examples show the intended name after publication.

What you get

• One dataset row per matching ERC-20 Transfer event, with actual event identifiers, addresses, block details and timestamps.
• Exact six-decimal token amounts, alongside convenient numeric display amounts.
• Optional transaction sender, destination, nonce, type and native value.
• Per-token totals, distinct transaction counts and largest transfers.
• Optional per-wallet incoming, outgoing and net flow summaries.
• Private incremental checkpoints for customer-configured Apify schedules.
• A coverage report explaining whether the requested search finished and how to continue it.

Use this Ethereum Whale Tracker for treasury reporting, stablecoin movement research, wallet activity pipelines and reproducible blockchain transaction data exports.

Use cases

• Treasury reporting: monitor large incoming and outgoing stablecoin transfers across selected wallets, with separate token totals and exact amounts.
• Stablecoin research: use the USDT Transfer Tracker and USDC Transaction Tracker to compare large movements over a bounded historical period.
• Data pipelines: run an Ethereum Wallet Monitor on an Apify schedule and join stable event identifiers to your own legally sourced analysis.

What a large transfer means

A large Transfer event establishes a token movement. It does not establish a whale purchase, sale, exchange deposit, wallet owner, profitability, or trading signal. USD values assume a $1 stablecoin peg; they are not market prices or depeg measurements. Zero-address transfers are returned as Transfer events without claiming minting or burning analysis.

Quick start

Select USDT, USDC or both, enter a minimum amount, choose a period and run. No Ethereum developer credentials are required from customers: provider access is configured by the operator.

For transfers of at least 500,000 token units during the last finalized hour:

{
  "tokens": ["USDT", "USDC"],
  "minimumTransfer": "500000",
  "timeRange": "last_hour",
  "maxResults": 1000,
  "includeTransactionDetails": true
}

Relative periods end at the latest finalized block, which trails the current chain head. This is periodic finalized-data retrieval, not real-time Stablecoin Whale Alerts. Review finality_lag_seconds and the exact effective timestamps in the coverage report.

Inputs

Input	Default	Description
Blockchain	Ethereum	Ethereum mainnet only
Tokens	USDT, USDC	Issuer-verified native token contracts
Minimum transfer	"100000"	Inclusive minimum per event, as a decimal string with up to six places
Time range	Last finalized hour	Also six hours, 24 hours or a custom UTC interval
Custom start/end	Empty	UTC timestamps; end exclusive, whole seconds, at most 24 hours within the previous 30 days
Wallet addresses	Empty	Up to 20 public Ethereum addresses
Wallet direction	Both	Incoming, outgoing or both for specified wallets
Maximum results	10	Raise up to 1,000 events when needed; a cap may leave incomplete coverage
Include transaction details	True	Additional reads for matching transactions
Incremental monitoring	False	Continue a private stream from its last committed position
Monitor name	default	Separate stream name; use a new name when changing filters
Historical continuation token	Empty	Continue an incomplete snapshot with the same filters

See the Input tab for descriptions and validation. An amount threshold applies to each Transfer event, not the sum of every transfer within one transaction.

Output and exports

Export the default dataset as JSON, CSV, Excel or other Apify dataset formats. amount_exact and amount_raw are authoritative; numeric amount is a convenient floating-point representation.

Abridged example from a verified real Ethereum transfer (shown for the output format; this small transfer is below the default threshold):

{
  "blockchain": "ethereum",
  "token": "USDT",
  "amount_exact": "100.000000",
  "amount_raw": "100000000",
  "estimated_usd_value": 100,
  "valuation_method": "assumed_usd_peg",
  "transaction_hash": "0xe7290f444909e22b9057847dca871d87cd5ce1e79e615b72df4a062114aa8f9e",
  "log_index": 1,
  "block_number": 26210884,
  "timestamp": "2026-10-17T07:48:59Z",
  "transfer_type": "token_transfer",
  "finality": "finalized"
}

Field	Type	Meaning
event_id	string	Chain ID, transaction hash and log index
blockchain, chain_id	string, integer	Ethereum and chain 1
token, token_contract	string	USDT/USDC and verified contract
amount, amount_exact, amount_raw	number, string, string	Display amount, exact six-place amount and uint256 base units
estimated_usd_value	number	Estimated value at an assumed $1 peg
valuation_method, assumed_usd_price	string, number	assumed_usd_peg, 1
from_address, to_address	string	Actual token event sender and recipient
transaction_hash, log_index	string, integer	Actual event identity
block_number, block_hash, transaction_index	integer, string, integer	Actual canonical block/event position
timestamp	string	Block timestamp in UTC
transaction_url	string	Etherscan transaction link
transfer_type, finality	string	token_transfer, finalized
transaction_details	object or null	Actual transaction-level fields when requested; transaction sender may differ from token sender

The accompanying OUTPUT report includes complete, failed, stop_reason, processing_limit_seconds, effective time range, next position, continuation token, provider work counters, token summaries and wallet summaries. Always inspect this report before treating a search as exhaustive. Summaries describe returned matching records, not every activity or the balance of a wallet. Selected tokens and watched wallets have explicit zero totals when no matching event is returned; check coverage before interpreting those zeroes. Self-transfers contribute to both incoming and outgoing volume, once to the event count, and zero to net flow.

For continuation or monitoring executions, complete means the remaining range after starting_position finished. Earlier pages remain in their original datasets. A continuation token is validated pagination data, not proof that earlier pages were retrieved; combine and deduplicate your retained pages when analyzing the original complete period.

Different Transfer events in the same transaction are separate records. Deduplicate downstream using event_id, not transaction hash alone.

Wallet monitoring and schedules

Add wallet addresses and enable incremental monitoring. Save the configuration as your own Apify task and configure an hourly schedule in Apify. Keep the same monitor name and filters. The Actor resumes from its checkpoint, including positions within a block, and does not create schedules or send notifications itself.

Monitoring storage belongs to the account running the Actor. Independent callers and monitor names do not share state. State and result stores created by the Actor are restricted. Account owners can still deliberately share their own data through Apify; treat exported files and shared run links accordingly.

After interruptions, confirmed dataset deliveries can be recovered without emitting them again. An unresolved append or charge outcome pauses the stream for review rather than risking duplicates or charging twice. There is no transactional exactly-once guarantee across arbitrary crashes. Preserve earlier run datasets until pending recovery is resolved.

Backlogs larger than 24 hours require bounded historical backfills before continuing the stream. Do not delete or reset a checkpoint to skip missing coverage unless that is your deliberate intention. Named monitoring storage persists until you delete it and incurs retention costs.

Introductory pricing

The introductory model is $0.005 per run + $0.075 per started hour searched + $1 per 1,000 delivered transfer events, including platform usage. Both tokens, wallet filters and optional transaction details are included. Check the Pricing tab for the effective prices before starting.

A one-hour search returning 10 events costs $0.09; 1,000 events cost $1.08. A zero-match one-hour search costs $0.08 if coverage is searched. The minimum allowed spending limit is $0.081; it is a budget floor, not a flat charge. A 24-hour search can cost up to $1.805 for coverage and startup, plus delivered events, but resource limits may require multiple executions. Each continuation is billed as a new execution for the coverage it searches.

Zero-match searches still perform work. The platform charges startup automatically, including runs that fail validation or cannot reach the provider. Coverage is charged after the first successful log response for each started hour; a later failure may leave a charged partial search. Transfer charges follow confirmed delivery. Retries and duplicate matches are not additional transfer events.

Set Apify's maximum total charge to control spending. The Actor stops when the next charge cannot fit and reports incomplete coverage. Stored datasets and named checkpoints persist under Apify's retention rules; customer exports and storage outside the execution may carry separate Apify costs. Prices can change under Apify's pricing notice rules.

API example

After publication, use the Apify Python client with your Apify token, not an Ethereum key:

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("thescrapelab/ethereum-stablecoin-whale-tracker").call(
    run_input={"minimumTransfer": "500000", "timeRange": "last_hour", "maxResults": 100},
    max_total_charge_usd=1,
)
summary = client.key_value_store(run.default_key_value_store_id).get_record("OUTPUT")["value"]
for row in client.dataset(run.default_dataset_id).iterate_items():
    print(row["token"], row["amount_exact"], row["event_id"])
print("Exhaustive:", summary["complete"], "Reason:", summary["stop_reason"])

Limitations and FAQ

Why is recent activity missing? Only finalized blocks are searched. The report exposes lag; unsupported or stale finality fails clearly instead of silently using the chain head.

Why did the search stop? Maximum results, raw events, response bytes, block count, RPC budget, runtime or charge limits can stop it. An incomplete historical search supplies a continuation token; monitoring uses its checkpoint. Provider and recovery errors require inspection before retrying.

Why does a high threshold still take work? ERC-20 amounts are not indexed. Global searches inspect raw Transfer events before filtering. Wallet filters usually reduce data retrieval.

Can I identify an exchange or wallet owner? No attribution data is supplied. Crypto Whale Movement Data is factual event evidence, not ownership intelligence.

Does it support Base, Bitcoin, other tokens or alerts? Not in v1. Additional EVM networks, notifications, mint/burn analysis and historical wallet intelligence are possible future extensions.

Can results be empty? Yes. A successfully completed empty search produces an empty dataset and an honest coverage report; it never fabricates a transaction to satisfy a health check.

How do I request support? Use this Actor's Issues tab in Apify and include the run ID and stop reason. Keep credentials and private wallet watchlists out of public issues.

Development and release evidence

See docs/FEASIBILITY.md, docs/VALIDATION.md, docs/LIVE_VERIFICATION_2026-10-17.md, and docs/COST_AND_PROFITABILITY.md. The examples/PROVENANCE.md distinguishes generated fixtures from verified live samples.