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,869,703The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 11,775,712 — 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 11,775,712 — the earliest block among the facts that earned it.No owner, immutable codeNo Ownable owner was ever set and the code cannot be replaced — there is no control surface to hold. Derived unambiguously from chain data. Known from block 11,775,712 — the earliest block among the facts that earned it.
BalanceNative ETH balance of this address, valued at $2,500.04/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 78. Activity through internal calls, events or token transfers is not counted here.
78
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".
9
Nature 3Architecture 1Presence 2Derived 3
Relationships
StructuralLinks derived from on-chain deployment and code identity
Deployed byThe account that executed the CREATE — often a factory contractZipmex MultiSig 1Zipmex MultiSig 1 (0x1bdac750132eb91e569f6fd2582d2d67f6f1ea0c)deploy txblock 11,775,7122021-02-02 08:22 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transactionZipmex Deployer 1Zipmex Deployer 1 (0x1fd5daa9bb707afb8a3197def72005757f8d1e36)
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 1.5M contracts
Timeline
11,775,712First block where this address appeared in on-chain state· 2021-02-02 · 5.6y ago14,485,355Newest block across the activity streams the platform could consult, inbound included. Events 14,485,355 · Token transfers — none · Internal transfers 14,485,355 · Direct transactions 14,485,355· 2022-03-30 · 4.4y ago
4.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 14,485,355 · Token transfers — none · Internal transfers 14,485,355 · Direct transactions 14,485,355
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,869,4694 of 4 counterparties
Zipmex MultiSig 1Zipmex MultiSig 1 (0x1bdac750132eb91e569f6fd2582d2d67f6f1ea0c)77 int77 with an internal call — reverts included, and one transaction can be several of these at once.This address was the sender in all of them (77); it received nothing from the other.last ~1581d agoLast: block 14,485,355 · ~2022-05-02. First ever: block 11,777,219 · ~2021-04-21. Dates estimated from the block distance.77 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
2Miners: PPLNS2Miners: PPLNS (0x00192fb10df37c9fb26829eb2cc623cd1bf599e8)65 dir65 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (65); it sent nothing to the other.last ~1581d agoLast: block 14,485,355 · ~2022-05-02. First ever: block 12,229,966 · ~2021-06-23. Dates estimated from the block distance.65 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Ethermine 2Ethermine 2 (0xea674fdde714fd979de3edf0f56aa9716b898ec8)11 dir11 direct transactions — reverts included, and one transaction can be several of these at once.This address was the recipient in all of them (11); it sent nothing to the other.last ~1896d agoLast: block 12,216,547 · ~2021-06-21. First ever: block 11,836,614 · ~2021-04-29. Dates estimated from the block distance.11 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x1525...90a20x15252f6eea7a04ab0376409c5cfc1fa55b0690a22 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 ~1953d agoLast: block 11,802,756 · ~2021-04-25. First ever: block 11,777,219 · ~2021-04-21. Dates estimated from the block distance.2 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.