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.
#25,865,770The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 4,727,362 — 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 4,727,362 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,457.29/ETH
< 0.000001 ETH
$<0.01
Direct transactionsTop-level transactions to or from this address: sent 0 / received 122. Activity through internal calls, events or token transfers is not counted here.
122
State changesHow many times this address's own account state changed — balance, nonce or code
124
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".
5
Nature 3Derived 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 4,727,3622017-12-13 20:30 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
4,727,362First block where this address appeared in on-chain state· 2017-12-13 · 8.7y ago22,177,360Newest block across the activity streams the platform could consult, inbound included. Events — none · Token transfers 22,177,360 · Internal transfers 8,728,141 · Direct transactions 8,728,141· 2025-04-01 · 1.4y ago
1.4y silent
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 22,177,360 · Internal transfers 8,728,141 · Direct transactions 8,728,141
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,865,5786 of 6 counterparties
Ethermine 2Ethermine 2 (0xea674fdde714fd979de3edf0f56aa9716b898ec8)62 dir62 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (62); it sent nothing to the other.last ~2380d agoLast: block 8,728,118 · ~2020-02-22. First ever: block 5,691,373 · ~2018-12-28. Dates estimated from the block distance.62 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Bitfinex: MultiSigBitfinex: MultiSig (0xfbb1b73c4f0bda4f67dca266ce6ef42f520fbb98)60 dir · 60 int60 direct transactions, 60 with an internal call — reverts included, and one transaction can be several of these at once.In 60 of them this address was the sender, in 60 the recipient — one transaction can be both, so the two do not add up to the total.last ~2380d agoLast: block 8,728,141 · ~2020-02-22. First ever: block 5,836,262 · ~2019-01-17. Dates estimated from the block distance.60 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x0031...45650x00315630fdbc5c74a168009af63feb87f78345652 tok2 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 (2); it sent nothing to the other.last ~2850d agoLast: block 5,345,027 · ~2018-11-10. First ever: block 5,345,025 · ~2018-11-10. Dates estimated from the block distance.2 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x998a...71370x998a7fd73446cd6532bf3058a270581730b271371 nft1 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 (1); it sent nothing to the other.last ~512d agoLast: block 22,177,360 · ~2025-04-04. First ever: block 22,177,360 · ~2025-04-04. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Bitstamp 2Bitstamp 2 (0x1522900b6dafac587d499a862861c0869be6e428)1 int1 with an internal call — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (1); it sent nothing to the other.last ~2396d agoLast: block 8,614,084 · ~2020-02-07. First ever: block 8,614,084 · ~2020-02-07. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x30d8...f1c30x30d8ad7cbfaca59d423b2346b81dbbda36e4f1c31 tok1 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 (1); it sent nothing to the other.last ~2746d agoLast: block 6,087,965 · ~2019-02-21. First ever: block 6,087,965 · ~2019-02-21. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.