Nothing listed, but signals found
This address is on none of the lists we check, and the score reflects that. The findings below describe its activity — read them before you send.
0x085adc5a4a1227b1c8aab9a962c03676fa18f1ddMeasured
- Age
- 3 months
- Transfers
- 99 in / 0 out
- Stablecoins
- $1,952,528 in$0 out
- Counterparties
- 2
- Chain
- Ethereum
Further analysis
New Ethereum address (48 days) with 9 inbound stablecoin transfers totaling ~$1.95M from only 2 counterparties, no outbound activity. One small $10 test inbound precedes the large inflows. No blocklist exposure or contract status.
An automated reading of the patterns below, not a finding of fact. The records themselves are listed underneath.
- Red flagEthereuminferred
Large inbound stablecoin volume on a very new address
A 48-day-old address received ~$1.95M in stablecoins across 9 inbound transfers with zero outbound. High-value inflows to a fresh, non-contract address can indicate a collection/mule wallet, but also fits a new treasury, OTC settlement, or personal custody setup. Data is too thin to distinguish.
- Red flagEthereuminferred
Only 2 counterparties for all inbound funds
All 9 inbound transfers came from just 2 unique counterparties. Concentrated funding sources can reflect a single payer or service, which is common for legitimate payroll, exchange withdrawals, or OTC desks, but also for a dedicated funnel account. No outbound activity yet to show fund movement.
- Red flagEthereuminferred
Small test-sized inbound before larger amounts
One inbound of ~$10 was recorded, consistent with a test transfer to validate the address before sending larger sums. This is a common pattern in both legitimate first-time transfers and in pre-staging an account for later use; it is weak evidence on its own.
- Green flagEthereuminferred
No blocklist or contract indicators
The address is not a contract, is not directly on any blocklist, and has no blocklisted neighbours in the sampled data. This lowers concern, though the sample is small (9 transfers) and absence of hits is not proof of legitimacy.
Chain by chain1 active of 3 reached
Ethereum
explorer- Transfers
- 9
- In / out
- 9 / 0
- Stablecoin in / out
- $1,952,528 / $0
- Counterparties
- 2
- Active for
- 34 days
- First seen
- 20 Aug 2026
- Last seen
- 24 Sept 2026
- Assets
- DAI, ETH
- Large inbound stablecoin volume on a very new addressA 48-day-old address received ~$1.95M in stablecoins across 9 inbound transfers with zero outbound. High-value inflows to a fresh, non-contract address can indicate a collection/mule wallet, but also fits a new treasury, OTC settlement, or personal custody setup. Data is too thin to distinguish.
- Only 2 counterparties for all inbound fundsAll 9 inbound transfers came from just 2 unique counterparties. Concentrated funding sources can reflect a single payer or service, which is common for legitimate payroll, exchange withdrawals, or OTC desks, but also for a dedicated funnel account. No outbound activity yet to show fund movement.
- Small test-sized inbound before larger amountsOne inbound of ~$10 was recorded, consistent with a test transfer to validate the address before sending larger sums. This is a common pattern in both legitimate first-time transfers and in pre-staging an account for later use; it is weak evidence on its own.
- 1 small incoming transfer(s)Stablecoin transfers of $100 or less arrived here, the smallest being $10.00. This is often a test send before a larger payment — but dusting attacks look the same, so it is context, not a warning.
- No blocklist or contract indicatorsThe address is not a contract, is not directly on any blocklist, and has no blocklisted neighbours in the sampled data. This lowers concern, though the sample is small (9 transfers) and absence of hits is not proof of legitimacy.
Measured
- 1 test-sized inbound transfers, smallest $10
No activity found on: Polygon, Arbitrum One.
Could not be checked: Base, BNB Chain. Nothing here rules anything in or out on those chains.
- Base was not scanned: the Etherscan API key in use does not cover it. A paid plan would include it.
- BNB Chain was not scanned: the Etherscan API key in use does not cover it. A paid plan would include it.
- Not scanned yet: Tron. An address can be active there without anything showing here.
- Outside this scan: OP Mainnet, Avalanche C-Chain.