all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
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`, is called once during package publication. This `init` function creates a new LP Coin using the `amm_interface::create_lp_coin` function, associating it with the `AF_LP` type and a constant value of 6. The package primarily interacts with the `amm_interface` module to initialize a new LP Coin type.
The `af_lp` package defines a single dummy struct `AF_LP`. Its `init` function, which is likely an entry point, calls `amm_interface::create_lp_coin` to create a new LP coin associated with the `AF_LP` type, passing a constant value of 5 and the transaction context. This suggests `af_lp` acts as a wrapper or configuration for an AMM interface, specifically for creating a liquidity pool token. The package itself doesn't manage any complex state or objects beyond the initial LP coin creation. No notable patterns like signature gating, time-gating, or admin caps are present in this module.
This package defines an `Nft` object with fields for ID, name, description, media URL, and attributes. The `create_nft_with_verification` function creates a new `Nft` object and associates its ID with a `Verification` object from the `0launchpad` module. The `update_nft_with_verification` function allows modifying an `Nft`'s name, description, media URL, and attributes, but only if the provided `Nft` ID matches the one registered in the `Verification` object. All other public/entry functions (init, mint_order, mint_nft, mint_edition_nft, update_nft) immediately abort, indicating they are either placeholders or not intended for direct use in this version. The package uses a `Kiosk` and `KioskOwnerCap` for managing `Nft` objects in the `update_nft_with_verification` function, suggesting a pattern of controlled ownership and modification.
The `af_lp` package defines a dummy `AF_LP` struct. Its single public function, `init`, is a module initializer that calls `amm_interface::create_lp_coin` to create a new LP coin associated with the `AF_LP` type and a constant value of 6. This suggests the package is a minimal wrapper for integrating with an AMM (Automated Market Maker) interface, likely to register a new LP token. There are no notable patterns like admin caps, time-gating, or dynamic fields present.
This package defines a dummy `AF_LP` object. Its single public function, `init`, is an entry point that calls `amm_interface::create_lp_coin` to register the `AF_LP` type as an LP coin within an Automated Market Maker (AMM) system. The `init` function takes an `AF_LP` object and a `TxContext` as arguments, consuming the `AF_LP` object in the process. The package itself doesn't manage any objects directly beyond this initial registration.
True specific-lot profit from 5 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).
nft_collectorRule-based labels, conservative precision.
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": "0xd1f074490ab4ea7830738617c02889dcc7e94e1a9221fb40f5c1ca0719e663d5",
"n_tx": 659,
"n_successful_tx": 659,
"n_distinct_epochs": 157,
"n_distinct_sponsors": 0,
"first_seen_cp": 82929820,
"last_seen_cp": 235322931,
"first_seen_ts_ms": 1732373984979,
"last_seen_ts_ms": 1768605356275,
"total_gas_spent_mist": 1741995420,
"n_self_sponsored_tx": 659,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
20,
15,
17,
18,
16,
21,
4,
3,
2,
1,
0,
14,
19,
23,
5,
13,
22,
6,
10,
12,
11,
7,
8
],
"primary_archetype": "nft_collector",
"labels": [
"nft_collector"
],
"label_confidence": [
0.675
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely Atlantic / E. South America.
area + brightness = call volume; hover for detail