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.WithdrawalsBeacon-chain validator withdrawals credited to this address — paid by the consensus layer, with no transaction behind them.GraphMoney flow and structure around this address.
#25,926,861The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 6,725,982 — 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 6,725,982 — 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 3. Activity through internal calls, events or token transfers is not counted here.
3
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".
7
Nature 3Presence 2Derived 2
Relationships
StructuralLinks derived from on-chain deployment and code identity
Deployed byThe account that executed the CREATE — often a factory contractBittrex: ControllerBittrex: Controller (0xa3c1e324ca1ce40db73ed6026c4a177f099b5770)deploy txblock 6,725,9822018-11-18 06:59 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x6cac...e21f0x6cace0528324a8afc2b157ceba3cdd2a27c4e21f
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 1.6M 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
6,725,982First block where this address appeared in on-chain state· 2018-11-18 · 7.8y ago13,627,131Newest block across the activity streams the platform could consult, inbound included. Events — none · Token transfers 13,627,131 · Internal transfers — none · Direct transactions 13,627,131· 2021-11-16 · 4.8y 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 — none · Token transfers 13,627,131 · Internal transfers — none · Direct transactions 13,627,131
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,0502 of 2 counterparties
Bitfinex: MultiSigBitfinex: MultiSig (0xfbb1b73c4f0bda4f67dca266ce6ef42f520fbb98)3 dir · 3 tok3 direct transactions, 3 with a token transfer — reverts included, and one transaction can be several of these at once.In 3 of them this address was the sender, in 3 the recipient — one transaction can be both, so the two do not add up to the total.last ~1708d agoLast: block 13,627,131 · ~2022-01-03. First ever: block 13,113,625 · ~2021-10-24. Dates estimated from the block distance.3 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x68dd...2d280x68dd5cbf738ae184be2d0b58e35f91cbddda2d283 tok3 with a token transfer — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (3); it sent nothing to the other.last ~1708d agoLast: block 13,627,104 · ~2022-01-03. First ever: block 13,113,606 · ~2021-10-24. Dates estimated from the block distance.3 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.