Worth a second look
If you do not know them, send a small test amount before the full one.
0x281e2a32e53f7fc21eeefb0642cb984c8a7cc71bMeasured
- Age
- 3 months
- Transfers
- 7837 in / 41 out
- Stablecoins
- $6,025 in$6,025 out
- Counterparties
- 10
- Chain
- Arbitrum One
Further analysis
New Arbitrum address (60 days) with 78 sampled transfers, 10 counterparties, and balanced stablecoin flow (~$6k in and out). A funneling pattern is flagged: 7 sources forwarded $5,607 with a median delay of ~2 minutes. No blocklist hits. Data is limited to one chain and a short history.
An automated reading of the patterns below, not a finding of fact. The records themselves are listed underneath.
- Red flagArbitrum One
Funds collected and forwarded to one address
$6,025 arrived from 7 different sources, and 93% of it ($5,607) went on to 0x2df1c5…3df7, held for a median of under an hour. This pass-through shape is what a collection wallet looks like — which may be an exchange deposit address, or a layering step.
- Red flagArbitrum Oneinferred
Rapid pass-through of inbound stablecoins
7 sources sent $6,025 in stablecoins and $5,607 was forwarded with a median delay of about 2 minutes. Fast consolidation and forwarding can indicate layering, but also fits normal treasury sweeping, exchange deposit routing, or payment processing.
- Red flagArbitrum Oneinferred
Many test-sized inbound transfers
22 of 78 sampled inbound transfers were test-sized, with a smallest amount of $0.00001. This can be address-verification or dusting behavior, but is also consistent with routine pre-transfer checks by counterparties.
- ContextArbitrum Oneinferred
Short account history limits assessment
The address is only 60 days old with 78 sampled transfers on a single chain. This is too thin to establish a normal baseline, so the funneling signal cannot be confirmed or dismissed from this data alone.
- Green flagArbitrum Oneinferred
No direct blocklist exposure
The address is not directly on any blocklist and has no blocklisted neighbours in the sampled data, which lowers concern relative to a flagged counterparty.
Chain by chain1 active of 3 reached
Arbitrum One
explorer- Transfers
- 78
- In / out
- 37 / 41
- Stablecoin in / out
- $6,025 / $6,025
- Counterparties
- 10
- Active for
- 50 days
- First seen
- 8 Aug 2026
- Last seen
- 26 Sept 2026
- Assets
- ETH, USDC
- Funds collected and forwarded to one address$6,025 arrived from 7 different sources, and 93% of it ($5,607) went on to 0x2df1c5…3df7, held for a median of under an hour. This pass-through shape is what a collection wallet looks like — which may be an exchange deposit address, or a layering step.
- Rapid pass-through of inbound stablecoins7 sources sent $6,025 in stablecoins and $5,607 was forwarded with a median delay of about 2 minutes. Fast consolidation and forwarding can indicate layering, but also fits normal treasury sweeping, exchange deposit routing, or payment processing.
- Many test-sized inbound transfers22 of 78 sampled inbound transfers were test-sized, with a smallest amount of $0.00001. This can be address-verification or dusting behavior, but is also consistent with routine pre-transfer checks by counterparties.
- 22 small incoming transfer(s)Stablecoin transfers of $100 or less arrived here, the smallest being under a cent. This is often a test send before a larger payment — but dusting attacks look the same, so it is context, not a warning.
- Short account history limits assessmentThe address is only 60 days old with 78 sampled transfers on a single chain. This is too thin to establish a normal baseline, so the funneling signal cannot be confirmed or dismissed from this data alone.
- No direct blocklist exposureThe address is not directly on any blocklist and has no blocklisted neighbours in the sampled data, which lowers concern relative to a flagged counterparty.
Measured
- 22 test-sized inbound transfers, smallest $0.00001
- $6,025 in from 7 sources, $5,607 forwarded to a single address, typically after under an hour
No activity found on: Ethereum, Polygon.
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.