Assaying · reading Robinhood Chain
Resolving the launch, reading the curve, replaying the tape and transfers, then the deployer's record. A few seconds on the public RPC.
Resolving the launch, reading the curve, replaying the tape and transfers, then the deployer's record. A few seconds on the public RPC.
2 wallets are linked by passing the token between them; together they bought 100.0% of all quote in. A heuristic, not proof of one owner.
2 trades from 1 wallet. Too little to say anything about demand.
Every flag is a fixed condition; definitions and thresholds.
| Side | Wallet | NVDA | Tokens | Block | Tx |
|---|---|---|---|---|---|
| sell | 0x6505…40Dc | 0.02645 | 1.64M | 70,931,524 | 0x70a4d9…2d3f00 ↗ |
| buy | 0x6505…40Dc | 0.03002 | 1.64M | 70,900,697 | 0x9d90f6…5cf915 ↗ |
| # | Wallet | Balance | Share |
|---|
No bonds posted for this token.
Connect the deployer wallet to post a bond. Anyone can challenge an open bond below.
Computed at block 72,700,807 in 3.1 s (resolve 1 ms, reads 81 ms, logs 2726 ms, deployer 274 ms). Sources: pons factory and curve contracts, the token's Transfer logs, and the Chainlink ETH/USD feed, all on Robinhood Chain via public RPC.
What this cannot tell you: intent, off-chain coordination, funding links between wallets, liquidity after graduation, or what the price will do. Full method and limits →
JSON: /api/assay/0x571d…198A · badge: /api/badge/…svg
