all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
counterparties · funders · clusters
Move packages this wallet published on-chain — what it shipped, not what it used.
This package defines a dummy `AF_LP` struct. Its single public function, `init`, takes an `AF_LP` object and a `TxContext`. The `init` function then calls `amm_interface::create_lp_coin` with the provided `AF_LP` object, a constant value of 7 (likely representing decimals or a specific LP type), and the transaction context. This suggests the package's primary role is to initialize or register a new LP coin type within an AMM interface, with the `AF_LP` struct serving as a marker for this new LP coin.
This package defines a dummy `AF_LP` object. Its `init` function, which is likely an entry point, creates a new LP Coin using the `amm_interface::create_lp_coin` function. This function takes the `AF_LP` object, a constant value `7` (likely representing a decimal precision or type identifier), and the transaction context as arguments. The package's sole purpose appears to be the initialization and registration of this specific LP Coin type within an AMM system. There are no other public functions, no dynamic fields, no admin caps, and no explicit vault/escrow or royalty mechanisms visible in this IR.
This package defines a dummy `AF_LP` struct. Its `init` function, which is called once during package publication, creates a new LP coin using the `amm_interface::create_lp_coin` function. This function takes the `AF_LP` struct, a constant value of 5 (likely representing decimals or a fixed parameter), and the transaction context as arguments. The package primarily interacts with the `amm_interface` module to initialize an LP coin associated with the `AF_LP` type. There are no other public or entry functions, nor any notable patterns like admin caps, time-gating, or dynamic fields.
The `af_lp` package defines a dummy `AF_LP` object type. Its single public function, `init`, takes an `AF_LP` object and a `TxContext` as input. This function immediately calls `amm_interface::create_lp_coin` with the provided `AF_LP` object, a constant value of 6, and the `TxContext`. This suggests the package's primary purpose is to initialize or register a new LP (Liquidity Pool) coin of type `AF_LP` within an external AMM (Automated Market Maker) interface. There are no other public functions, dynamic fields, admin caps, or vault/escrow patterns present.
This package defines a dummy `AF_LP` object. Its `init` function calls `amm_interface::create_lp_coin` to create a new LP coin associated with the `AF_LP` type and a constant value of 5. This suggests the package primarily serves to register a liquidity pool token type within an AMM system. There are no other public or entry functions, and no notable patterns like admin caps, time-gating, or dynamic fields are present.
True specific-lot profit from 1 closed buy→sell round-trips of the same NFT (realized_roundtrip), wash-adjusted, valued at each leg's trade-hour USD. Excludes still-held inventory (that's unrealized).
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
Wallets that share a funder, were co-funded by the same personal-scale source, or land in the same behavioral cluster. A heuristic, not proof of common control.
Where this wallet's SUI first came from, and what it seeded downstream. Observational: a CEX funder suggests a real/retail origin; a high-fanout non-CEX funder is a signal worth noting — not proof of anything.
{
"wallet": "0xc2f45aa0ee89058023c1bbfd64a710d43ec5f6b16e52590bbad92d6a09a235e6",
"n_tx": 5217,
"n_successful_tx": 5062,
"n_distinct_epochs": 330,
"n_distinct_sponsors": 2,
"first_seen_cp": 23799422,
"last_seen_cp": 283511688,
"first_seen_ts_ms": 1705500839995,
"last_seen_ts_ms": 1780681164405,
"total_gas_spent_mist": 19227130284,
"n_self_sponsored_tx": 5214,
"n_sponsored_tx": 3,
"gas_price_p50": 504.95505,
"gas_price_p95": 750,
"active_hours_top24": [
13,
15,
17,
14,
12,
16,
20,
19,
18,
11,
9,
10,
8,
21,
7,
23,
22,
0,
5,
6,
1
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Tinted amber on the bubble map when they appear in the expanded graph.
Top active hours by UTC. Circadian peak → likely UK / W. Europe / W. Africa.
area + brightness = call volume; hover for detail