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 Sui package defines a single module `sc` which primarily manages a `BondingCurveStartCap<SC>` object. The `init` function is the only public/entry point, and it creates a new bonding curve using the `bonding_curve::create_bonding_curve` function. This bonding curve is initialized with metadata including a name ("Splash Cat"), description, image URL, and various social media links. The `init` function then transfers the newly created `BondingCurveStartCap<SC>` to the sender of the transaction. The module does not exhibit patterns like signature/allowlist gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties.
This package defines a single module `sc` which primarily manages a dummy `SC` object. The `init` function is the only public/entry point, and it creates a `BondingCurveStartCap<SC>` object using the `bonding_curve` module. This `BondingCurveStartCap` is then transferred to the transaction sender. The `init` function populates the bonding curve with metadata including a name, description, image URL, and various social media links (website, Twitter, Discord, Telegram), along with a large byte string that might represent initial curve parameters or data. This package appears to be a minimal setup for launching a bonding curve for a token represented by the `SC` type, with the `BondingCurveStartCap` acting as an administrative or initial control object.
This package defines a single module `sc` which manages a primary object type `SC` (a dummy struct). The `init` function is the only public/entry function and it creates a new `bonding_curve::BondingCurveStartCap<SC>` object, initializing it with various metadata including a name, description, image URL, and social media links. This `BondingCurveStartCap` is then transferred to the transaction sender. The module utilizes the `bonding_curve` module, `option`, `string`, `transfer`, `tx_context`, and `url` modules from the Sui framework. Notably, it uses a URL and several social media links, and a large hexadecimal string, likely for cryptographic or identifier purposes within the bonding curve.
This Sui package defines a single module `sc` which manages a primary object type `SC` (though `SC` itself is a dummy struct). The `init` function is the only public/entry function; it creates a `BondingCurveStartCap<SC>` object using the `bonding_curve` module, initializing it with various metadata including a name, description, image URL, and social media links. This `BondingCurveStartCap<SC>` is then transferred to the transaction sender. The package utilizes the `bonding_curve` module for its core functionality, `option` for optional URL fields, `string` for UTF8 strings, `transfer` for object ownership, `tx_context` for sender information, and `url` for URL handling. There are no notable patterns like signature/allowlist gating, time-gating, dynamic fields, admin caps, or royalties directly implemented in this module, but the `BondingCurveStartCap` suggests an underlying bonding curve mechanism.
This package defines a single dummy object type, `SC`, which holds a boolean. The `init` function is the only public/entry function, and it creates a `BondingCurveStartCap<SC>` object using the `bonding_curve` module. This `BondingCurveStartCap` is then transferred to the transaction sender. The `init` function populates the bonding curve with metadata including a name, description, image URL, and various social media links (website, Twitter, Discord, Telegram). A notable pattern is the use of the `bonding_curve` module to initialize a new bonding curve for the `SC` type, and the extensive use of string literals for metadata.
True specific-lot profit from 22 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).
1 self-dealing round-trip excluded from the headline (gross incl. wash: $980).
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.
Tinted amber on the bubble map when they appear in the expanded graph.
nft_collectorflippernft_traderRule-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": "0xc4c1957fe5c8241b4c0ea04773a521d711a6674964f27ada06b585a219afb1c8",
"n_tx": 1588,
"n_successful_tx": 1535,
"n_distinct_epochs": 236,
"n_distinct_sponsors": 1,
"first_seen_cp": 6393624,
"last_seen_cp": 237197163,
"first_seen_ts_ms": 1688067270345,
"last_seen_ts_ms": 1769089883244,
"total_gas_spent_mist": 10812177316,
"n_self_sponsored_tx": 1587,
"n_sponsored_tx": 1,
"gas_price_p50": 750,
"gas_price_p95": 810,
"active_hours_top24": [
16,
15,
14,
17,
13,
6,
10,
5,
7,
3,
12,
4,
9,
1,
11,
21,
18,
20,
2,
0,
8,
19,
23,
22
],
"primary_archetype": "nft_collector",
"labels": [
"nft_collector",
"flipper",
"nft_trader"
],
"label_confidence": [
0.68,
0.635,
0.613
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely C. Europe / Africa / Middle East.
area + brightness = call volume; hover for detail