Product guide

How to find transfers, use filters, and read the results.

Values in this guide are the current configuration defaults.

What the monitor does

Stablecoin Whale Monitor records large USDC and USDT transfers on Ethereum mainnet and shows them newest first. You can narrow the list, open any transfer to see its full record, look up a transaction, and follow links to Etherscan to check each record against the chain.

The monitor is public and read-only. There is no sign-in and no wallet connection.

What qualifies

A transfer is recorded when all of these are true:

It is a Transfer event from the USDC contract 0xa0b8…eb48 or the USDT contract 0xdac1…1ec7 on Ethereum mainnet (chain ID 1).
Its amount is at or above the indexing threshold, currently 100,000 tokens. Both tokens use 6 decimals.
Its block is at least 6 blocks behind the newest block.

Transfers under the threshold are never stored. Lowering the minimum amount filter below 100,000 cannot show them.

Filtering the feed

Three filters can be combined. Each applied filter appears as a chip above the results. Remove a chip to drop that filter, or use Reset all.

Filter	Accepts	Matches
Token	All, USDC or USDT	Transfers of that token
Minimum amount	A number with up to 6 decimal places. Commas are removed	Transfers at or above the amount, in tokens
Address	`0x` plus 40 hexadecimal characters	Transfers where the address is the sender or the receiver

Copy the page URL to share your filters, for example /monitor/?token=USDT&min=250000. The total counts all transfers that match your filters across all pages. The per-token counts split that total into USDC and USDT.

Results are pages of 50. Use Older and Newer to move between pages. Shared links always open at the newest transfers.

Looking up a transaction

Paste a transaction hash to find matching transfers in the last 7 days. A single transaction may contain several matching transfers.

Reading transfer details

Select a transfer to view its details. Automatic refresh pauses while the details are open. Copy the URL to share the selected transfer.

Field	Meaning
Amount	The full amount in token units, with an abbreviated value alongside it.
Raw amount	The same value as an integer in base units. With 6 decimals, 1 token is 1,000,000 base units.
From, To	Sender and receiver addresses in full. Addresses are not labeled and do not identify their owners.
Transfer type	Mint, burn or transfer. See below.
Block, block time	Where and when the transfer happened on chain, in UTC.
Log index	The position of this event inside its block. Together with the transaction hash it identifies the transfer.
Transaction	The transaction hash, with a link to Etherscan.
Token contract	The USDC or USDT contract that emitted the event.
Detected at	When the indexer recorded the transfer. It is later than the block time by the confirmation buffer and polling delay.
Threshold	The indexing threshold in force when the transfer was recorded.

Mint and burn

Classification uses only the zero address, 0x0000…0000:

Mint. The sender is the zero address. New tokens were created.
Burn. The receiver is the zero address. Tokens were removed from supply.
Everything else is a normal transfer.

Not every change in supply shows up this way. USDT issuance and redemption, for example, use the contract's own Issue and Redeem events rather than a Transfer to or from the zero address, so they are not indexed as mints or burns.

Freshness

A transfer is not shown the moment it is mined. It passes through four steps:

Confirmation
6 blocks, about 72 s
Indexer poll
Up to 30 s
API refresh
Up to 30 s
Monitor refresh
Up to 30 s, or press Refresh now

The configured confirmation and refresh intervals suggest a delay of roughly 1 to 3 minutes. The status strip at the top of the monitor shows three signals to help you check freshness:

API: whether the last request succeeded.
Index refreshed: when the API last reloaded stored transfers.
Chain progress: the last block the indexer finished and how old that checkpoint is.

The confirmation buffer reduces exposure to chain reorganizations but is not a finality guarantee. Records already published are not rewritten if a deeper reorganization happens.

Retention

The monitor keeps 7 days of transfers, based on block time. Totals can decrease as older transfers expire.

Maintenance

During maintenance, the monitor and status pages show the expected return date.

After a long pause, history can start later than 7 days ago. The monitor shows the date history starts from until the full window has filled in again.

Common questions

A transfer is on Etherscan but not in the monitor. Why?: It may be under 100,000 tokens, a different token, older than 7 days, or too recent to have passed the confirmation buffer and refresh cycle. Check the status page if you expected it within the last few minutes.
Can I see the value in US dollars?: No. Amounts are token units as recorded on chain. The monitor does not price tokens.
Who owns this address?: The monitor does not know. It shows addresses only. Any label you find elsewhere is that source's claim.
Why did the total change when nothing new arrived?: Transfers older than 7 days are removed continuously, so totals can fall between refreshes.
Why did I get "That page is no longer available"?: Pages after the first are anchored to a specific transfer. When that transfer ages out of the 7-day window, the page can no longer be built. The monitor starts again from the newest transfers.
Can I get alerts for large transfers?: Transfer alerts are currently unavailable.
Is a recorded transfer final?: It has at least 6 confirmations, which makes a reversal unlikely but not impossible. Records are not rewritten after a deep reorganization.

Found a problem in this page? Open an issue in the repository.