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,928,245The chain head this page was rendered at.
ContractThe address carries runtime code. Derived unambiguously from chain data. Known from block 5,343,805 — 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,343,805 — 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 13. Activity through internal calls, events or token transfers is not counted here.
13
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 contractUpbit Wallet Factory ContractUpbit Wallet Factory Contract (0x4f01001cf69785d4c37f03fd87398849411ccbba)deploy txblock 5,343,8052018-03-29 15:52 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transactionUpbit 5Upbit 5 (0x03747f06215b44e498831da019b27f53e483599f)
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 722.3K 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
5,343,805First block where this address appeared in on-chain state· 2018-03-29 · 8.4y ago14,767,112Newest block across the activity streams the platform could consult, inbound included. Events — none · Token transfers 14,767,112 · Internal transfers — none · Direct transactions 14,767,112· 2022-05-13 · 4.3y 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 14,767,112 · Internal transfers — none · Direct transactions 14,767,112
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,05014 of 14 counterparties
MEV BotMEV Bot (0x1938a448d105d26c40a52a1bfe99b8ca7a745ad0)6 dir · 6 tok6 direct transactions, 6 with a token transfer — reverts included, and one transaction can be several of these at once.In 6 of them this address was the sender, in 6 the recipient — one transaction can be both, so the two do not add up to the total.last ~1549d agoLast: block 14,767,112 · ~2022-06-11. First ever: block 12,183,242 · ~2021-06-17. Dates estimated from the block distance.6 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Upbit 2Upbit 2 (0xba826fec90cefdf6706858e5fbafcb27a290fbe0)4 dir · 4 tok4 direct transactions, 4 with a token transfer — reverts included, and one transaction can be several of these at once.In 4 of them this address was the sender, in 4 the recipient — one transaction can be both, so the two do not add up to the total.last ~2573d agoLast: block 7,392,289 · ~2019-08-21. First ever: block 6,794,367 · ~2019-05-30. Dates estimated from the block distance.4 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0xfea4...5e830xfea4f258a3bf1a3a4b7431a98acf4bcba0b75e833 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 ~1553d agoLast: block 14,739,299 · ~2022-06-07. First ever: block 13,580,375 · ~2021-12-28. Dates estimated from the block distance.3 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Upbit 5Upbit 5 (0x03747f06215b44e498831da019b27f53e483599f)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 ~2823d agoLast: block 5,598,060 · ~2018-12-15. First ever: block 5,343,999 · ~2018-11-10. Dates estimated from the block distance.3 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Bithumb 19Bithumb 19 (0x22b84d5ffea8b801c0422afe752377a64aa738c2)2 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 ~2852d agoLast: block 5,386,352 · ~2018-11-16. First ever: block 5,343,927 · ~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.
0x3bfd...a6a40x3bfdea17c92c933eb2c7d38aa503b249e7e6a6a41 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 ~1725d agoLast: block 13,497,880 · ~2021-12-16. First ever: block 13,497,880 · ~2021-12-16. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0x5cc7...71540x5cc7a0dfdbedad286c3a28ea615e230076cf71541 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 ~1764d agoLast: block 13,223,758 · ~2021-11-08. First ever: block 13,223,758 · ~2021-11-08. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Binance 7 (Hot Wallet)Binance 7 (Hot Wallet) (0x3f5ce5fbfe3e9af3971dd833d26ba9b5c936f0be)1 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 ~1909d agoLast: block 12,180,046 · ~2021-06-16. First ever: block 12,180,046 · ~2021-06-16. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
DisperseDisperse (0x99fbbfb44c53ba981e1d835313bd5e0043441c3e)1 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 ~2524d agoLast: block 7,748,098 · ~2019-10-10. First ever: block 7,748,098 · ~2019-10-10. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Bithumb 492Bithumb 492 (0xcea469b7f33a7b9083ddf0890c419b5858638e30)1 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 ~2574d agoLast: block 7,391,998 · ~2019-08-21. First ever: block 7,391,998 · ~2019-08-21. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Bithumb 506Bithumb 506 (0xdc6afc9db17550fd1074431ed66809576d19e514)1 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 ~2582d agoLast: block 7,333,033 · ~2019-08-13. First ever: block 7,333,033 · ~2019-08-13. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
0xf80f...e18b0xf80f6d4a340f3265e0eec52c07024bd3ed0ee18b1 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 ~2583d agoLast: block 7,326,628 · ~2019-08-12. First ever: block 7,326,628 · ~2019-08-12. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Bithumb 488Bithumb 488 (0x67cdacacc9342b2f279333bccf48880f37cd4a69)1 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 ~2657d agoLast: block 6,794,295 · ~2019-05-30. First ever: block 6,794,295 · ~2019-05-30. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.
Bithumb: Deposit Funder 3Bithumb: Deposit Funder 3 (0x83761c6785427f5a27a07c92a9dcfa99947bc4ad)1 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 ~2823d agoLast: block 5,598,013 · ~2018-12-15. First ever: block 5,598,013 · ~2018-12-15. Dates estimated from the block distance.1 txTransactions where the two interacted — direct, token or internal. Ranked by the ones that succeeded.