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 `init` function, which runs once on package publication, calls `amm_interface::create_lp_coin` to register a new LP coin type associated with `AF_LP` and a constant value of 9. This suggests the package is a minimal wrapper to integrate a specific LP token into an AMM (Automated Market Maker) system. There are no other public or entry functions, meaning no further direct interactions with `AF_LP` objects are possible within this package. The package primarily serves to initialize an LP coin within an external AMM.
This package manages Chain objects, which represent a sequence of Fragment objects. Users can create a Chain, add, edit, move, or remove Fragments within an unlocked Chain. The `lock_chain` function prevents further modifications to a Chain. A Chain can be burned if it's locked and empty. The `publish_all` function takes a locked Chain and its associated Fragments, verifying their integrity, and then creates immutable PublishedChain and PublishedFragment objects, freezing them for public access. Finally, `mint_fragment` allows users to create a MintedFragment from a PublishedFragment, transferring ownership to a specified address. The package uses time-gating for creation and update timestamps and includes checks to ensure Chain objects are unlocked for modifications and locked for publishing or burning.
The `af_lp` package defines a dummy `AF_LP` struct, which is likely a placeholder for a liquidity provider token. Its single `init` function, which is an entry point, calls `amm_interface::create_lp_coin` to register this `AF_LP` type as a new LP coin within an AMM (Automated Market Maker) system. This function takes the `AF_LP` struct and a `TxContext` as arguments, suggesting it's designed to be called once upon package deployment to initialize the LP token. The package primarily interacts with the `amm_interface` module, indicating its role in an AMM ecosystem. There are no notable patterns like signature gating, time-gating, or admin caps present in this module.
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": "0xd6ed19aac25ee4986feb1bd0c1ee988b7226d39634092b6b898f2f87a015d216",
"n_tx": 27869,
"n_successful_tx": 18269,
"n_distinct_epochs": 213,
"n_distinct_sponsors": 1,
"first_seen_cp": 207513244,
"last_seen_cp": 283586366,
"first_seen_ts_ms": 1762036535667,
"last_seen_ts_ms": 1780697792300,
"total_gas_spent_mist": 39885976790,
"n_self_sponsored_tx": 27868,
"n_sponsored_tx": 1,
"gas_price_p50": 508.86685,
"gas_price_p95": 557,
"active_hours_top24": [
15,
14,
16,
13,
17,
18,
0,
19,
1,
20,
6,
2,
22,
5,
12,
9,
23,
21,
8,
7,
11,
10,
4,
3
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"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