OverviewWhat this address is, since when, and how it is doing.TransactionsTransactions of this address and everything inside them — transfers, internal calls, state and storage changes, emitted events, DEX trades.HoldersWho holds this asset now, ranked by balance.PoolsDEX pools this asset trades in, and its recent volume.GraphMoney flow and structure around this address.
#25,934,703The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 16,200,722 — the earliest block among the facts that earned it.Code deployed onceThe contract carries code, and that code was placed here once — never removed and re-created. Derived unambiguously from chain data. Known from block 16,200,722 — the earliest block among the facts that earned it.Contract-controlledThe owner is a contract — a timelock, a governor or another program stands between a key and this contract. What that contract allows is its own question. Derived unambiguously from chain data. Known from block 16,200,722 — the earliest block among the facts that earned it.ERC-721 in codeThe ERC-721 selector set is present in the code that actually executes. It does not say the collection has ever minted or moved anything: of 11.4M addresses with this interface, 1.3% have emitted a token event. Derived unambiguously from chain data. Known from block 16,200,722 — the earliest block among the facts that earned it.NFT extensionsThe optional NFT interfaces this code carries — metadata, enumeration, royalties, multi-token. Presence in the code, not a promise that any of them is honoured. Derived unambiguously from chain data. Known from block 16,200,722 — the earliest block among the facts that earned it.Privileged functionsThe executing code exposes mint, pause or blacklist functions — presence in the dispatch table, NOT proof that they can be called now, or by whom. The ones found are listed with it. Derived unambiguously from chain data. Known from block 16,200,722 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,489.03/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 2. Activity through internal calls, events or token transfers is not counted here.
2
State changesHow many times this address's own account state changed — balance, nonce or code
1
Fees paidTotal gas fees this address has paid as a sender, all time.
0 ETH
DormantNo activity of any kind for over a year — transactions, internal calls, events and token transfers alike
Chain factsDerived unambiguously from chain data. Each fact is stated only when it was proven — a fact that is absent was not proven, which is not the same as "no".
StructuralLinks derived from on-chain deployment and code identity
Deployed byThe account that executed the CREATE — often a factory contract0x1f35...b5640x1f35e5ee0eaf6c2dc7a77f690f9021ce4788b564deploy txblock 16,200,7222022-12-17 00:05 UTC
Owned byThe current owner of this contract, by its last ownership transfer (OpenZeppelin Ownable). Role-based access control is a different pattern and is not covered by this.0xbe28...dd080xbe28f1bcb5d5182890f6c025984dedda764bdd08seen at 16,200,873Where the platform last observed this owner. Not a start: no history is built for this relation.
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 2 contracts
Timeline
LondonLondon · block 12,965,000. EIP-1559: blocks carry a base fee, and part of every fee is burnt.MergeMerge · block 15,537,394. Proof of stake. Difficulty goes to zero and block times settle at 12 seconds.ShapellaShapella · block 17,034,871. Validator withdrawals begin — the first stake leaves the beacon chain.DencunDencun · block 19,426,587. EIP-4844: blob-carrying transactions, with their own gas market.PectraPectra · block 22,431,084. EIP-7702: an EOA can carry a delegation to contract code.FusakaFusaka · block 23,935,694. Blob capacity steps up on a schedule of its own (BPO), past the Pectra ceiling.
5M10M15M20M25M
16,200,722First block where this address appeared in on-chain state· 2022-12-17 · 3.7y ago16,200,873Newest block across the activity streams the platform could consult, inbound included. Events 16,200,873 · Token transfers — none · Internal transfers — none · Direct transactions 16,200,873· 2022-12-17 · 3.7y ago
First seenFirst block where this address appeared in on-chain state
Last activeNewest block across the activity streams the platform could consult, inbound included. Events 16,200,873 · Token transfers — none · Internal transfers — none · Direct transactions 16,200,873
Ranked by how OFTEN the two interacted, not by how much value passed — that is the Graph. Ordered, not numbered: hundreds can sit tied at the tail.Every interaction the graph holds, as of the block named beside itall time · as of block 25,925,0501 of 1 counterparties
0x1f35...b5640x1f35e5ee0eaf6c2dc7a77f690f9021ce4788b5642 dir2 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (2); it sent nothing to the other.last ~1350d agoLast: block 16,200,873 · ~2022-12-28. First ever: block 16,200,816 · ~2022-12-28. Dates estimated from the block distance.2 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.