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.
The `af_lp` package defines a dummy `AF_LP` struct. Its single public function, `init`, takes an `AF_LP` object and a `TxContext`, then calls `amm_interface::create_lp_coin` with the `AF_LP` object, a constant value (9), and the `TxContext`. This suggests the package is primarily concerned with initializing a liquidity pool coin representation within an AMM interface, likely for a specific asset type, but the `AF_LP` struct itself holds no meaningful data.
This package defines a dummy `AF_LP` object. Its `init` function, which is likely called once during package deployment, registers the `AF_LP` type as a liquidity pool coin with the `amm_interface` module, using a constant value of 9. This suggests `AF_LP` is intended to represent a specific type of LP token within an Automated Market Maker (AMM) system. The package itself does not contain any other public or entry functions, nor does it manage any other objects or implement complex patterns like vaulting or time-gating.
This package defines a dummy `AF_LP` struct. Its single public function, `init`, takes an `AF_LP` object and a `TxContext`. The `init` function immediately calls `amm_interface::create_lp_coin` with the provided `AF_LP` object, a constant value of 9 (likely representing a decimal precision or type identifier), and the transaction context. This suggests the package's primary purpose is to register or initialize a new LP (Liquidity Provider) coin type within an AMM (Automated Market Maker) system, using the `AF_LP` struct as a placeholder or identifier for this LP coin. The `AF_LP` object itself is not mutated beyond its initial creation and use in the `create_lp_coin` call.
This package defines a dummy `AF_LP` object. Its `init` function, which acts as a constructor, takes an `AF_LP` object and a `TxContext` as input. The `init` function then calls `amm_interface::create_lp_coin` with the provided `AF_LP` object, a constant value of 9, and the `TxContext`. This suggests the package is primarily concerned with initializing or registering a liquidity pool (LP) coin within an Automated Market Maker (AMM) system, likely using the `AF_LP` object as a marker or identifier for this specific LP. There are no other public or entry functions, dynamic fields, or complex access control mechanisms visible in this IR.
This Sui package defines a single module `af_lp` that manages a dummy `AF_LP` object. Its only public function, `init`, is called once at package deployment. This function creates a new LP coin using the `amm_interface::create_lp_coin` function, passing the `AF_LP` object, a constant value `9`, and the transaction context. The package itself doesn't define any other public or entry functions, nor does it manage any state beyond the initial LP coin creation. It appears to be a minimal wrapper for integrating with an AMM (Automated Market Maker) interface, likely to register `AF_LP` as a liquidity provider token.
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.
Tinted amber on the bubble map when they appear in the expanded graph.
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": "0xa87bd0082f4fbfccb239fb4d2c2f581c40f9e0997f5f0441559afeef86cc0197",
"n_tx": 240,
"n_successful_tx": 236,
"n_distinct_epochs": 23,
"n_distinct_sponsors": 0,
"first_seen_cp": 171224049,
"last_seen_cp": 264682508,
"first_seen_ts_ms": 1753377267096,
"last_seen_ts_ms": 1776119026915,
"total_gas_spent_mist": 503592012,
"n_self_sponsored_tx": 240,
"n_sponsored_tx": 0,
"gas_price_p50": 500,
"gas_price_p95": 505,
"active_hours_top24": [
3,
16,
14,
20,
19,
6,
18,
5,
15,
23,
4,
10,
17,
0,
13,
2,
22,
11
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).
area + brightness = call volume; hover for detail