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,864,117The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 5,050,042 — 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 5,050,042 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,451.83/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 5. Activity through internal calls, events or token transfers is not counted here.
5
State changesHow many times this address's own account state changed — balance, nonce or code
6
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 5,050,0422018-02-08 00:42 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
5,050,042First block where this address appeared in on-chain state· 2018-02-08 · 8.6y ago6,677,176Newest block across the activity streams the platform could consult, inbound included. Events — none · Token transfers — none · Internal transfers 6,677,176 · Direct transactions 6,677,176· 2018-11-10 · 7.8y ago
7.8y 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 — none · Internal transfers 6,677,176 · Direct transactions 6,677,176
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,863,8022 of 2 counterparties
0x542a...2d8c0x542a4024afc4914cd9e6954cae7fae3da9dc2d8c3 dir3 direct transactions — 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 ~2664d agoLast: block 6,677,165 · ~2019-05-14. First ever: block 6,654,755 · ~2019-05-11. Dates estimated from the block distance.3 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Bitfinex: MultiSigBitfinex: MultiSig (0xfbb1b73c4f0bda4f67dca266ce6ef42f520fbb98)2 dir · 2 int2 direct transactions, 2 with an internal call — reverts included, and one transaction can be several of these at once.In 2 of them this address was the sender, in 2 the recipient — one transaction can be both, so the two do not add up to the total.last ~2664d agoLast: block 6,677,176 · ~2019-05-14. First ever: block 6,654,770 · ~2019-05-11. Dates estimated from the block distance.2 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.