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.GraphMoney flow and structure around this address.
ContractThe address currently carries runtime code. Derived unambiguously from chain data.Had runtime codeRuntime code existed at this address at some point of its history. Derived unambiguously from chain data.
BalanceNative ETH balance of this address, valued at $2,456.60/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 14. Activity through internal calls, events or token transfers is not counted here.
14
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
Timeline
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 — none · Token transfers — none · Internal transfers — none · Direct transactions 17,288,870
DormantNo activity of any kind for over a year — transactions, internal calls, events and token transfers alikeNo active blacklistsChecked against known issuer blacklists — none currently lists this address
Portfolio
ETH
$0.00
0 ETH
Total (shown tokens + ETH)
≈ $0.00
CapabilitiesStructural abilities of the code, derived by the platform from bytecode and storage analysis
No proxy or upgrade mechanics detectedStatic analysis found no delegatecall-based upgrade path or proxy mechanics in the runtime bytecode4 functionsDistinct function selectors found in the runtime bytecode
Relationships
StructuralLinks derived from on-chain deployment and code identity
Deployed byThe account that executed the CREATE — often a factory contract0xc020...67830xc02042f9a16501b0ef5ec3679d9191bc857d6783deploy txblock 17,204,4852023-05-06 22:22 UTC
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 1 contract
Top counterparties
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,839,8801 of 1 counterparties
0xc020...67830xc02042f9a16501b0ef5ec3679d9191bc857d678314 dir14 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (14); it sent nothing to the other.last ~1187d agoLast: block 17,288,870 · ~2023-05-26. First ever: block 17,205,921 · ~2023-05-15. Dates estimated from the block distance.9 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded. 5 more reverted.