Ethereum Explorer
Blocks
Status
Address
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0.
000
313
053
994
722
ETH
Confirmed
Balance
0.
000
313
053
994
722
ETH
Transactions
153
Non-contract Transactions
153
Internal Transactions
0
Nonce
143
ERC20 Tokens
45
Contract
Quantity
Value
Transfers
#
A Next-Generation Smart Contract and Decentralized Application Platform Satoshi Nakamoto's development of Bitcoin in 2009 has often been hailed as a radical development in money and currency, being the first example of a digital asset which simultaneously has no backing or *intrinsic value(opens in a new tab)* and no centralized issuer or controller. However, another, arguably more important, part of the Bitcoin experiment is the underlying blockchain technology as a tool of distributed consensus, and attention is rapidly starting to shift to this other aspect of Bitcoin. Commonly cited alternative applications of blockchain technology include using on-blockchain digital assets to represent custom currencies and financial instruments (*colored coins(opens in a new tab)*), the ownership of an underlying physical device (*smart property(opens in a new tab)*), non-fungible assets such as domain names (*Namecoin(opens in a new tab)Ü), as well as more complex applications involving having digital assets being directly controlled by a piece of code implementing arbitrary rules (*smart contracts(opens in a new tab)*) or even blockchain-based *decentralized autonomous organizations(opens in a new tab)* (DAOs). What Ethereum intends to provide is a blockchain with a built-in fully fledged Turing-complete programming language that can be used to create *contracts* that can be used to encode arbitrary state transition functions, allowing users to create any of the systems described above, as well as many others that we have not yet imagined, simply by writing up the logic in a few lines of code.
0.
811
313
480
788
085
938
GENESIS
2
AI SPIRAL
0.
909
818
523
314
411
102
SPIRAL
3
Along Came A Cat
0.
431
431
174
003
309
04
CAT
3
Bitcoin As A State Transition System From a technical standpoint, the ledger of a cryptocurrency such as Bitcoin can be thought of as a state transition system, where there is a *state* consisting of the ownership status of all existing bitcoins and a *state transition function* that takes a state and a transaction and outputs a new state which is the result. In a standard banking system, for example, the state is a balance sheet, a transaction is a request to move $X from A to B, and the state transition function reduces the value in A's account by $X and increases the value in B's account by $X. If A's account has less than $X in the first place, the state transition function returns an error. Hence, one can formally define: The *state* in Bitcoin is the collection of all coins (technically, *unspent transaction outputs* or UTXO) that have been minted and not yet spent, with each UTXO having a denomination and an owner (defined by a 20-byte address which is essentially a cryptographic public keyfn1). A transaction contains one or more inputs, with each input containing a reference to an existing UTXO and a cryptographic signature produced by the private key associated with the owner's address, and one or more outputs, with each output containing a new UTXO to be added to the state. The state transition function APPLY(S,TX) -> S' can be defined roughly as follows: For each input in TX: If the referenced UTXO is not in S, return an error. If the provided signature does not match the owner of the UTXO, return an error. If the sum of the denominations of all input UTXO is less than the sum of the denominations of all output UTXO, return an error. Return S with all input UTXO removed and all output UTXO added The first half of the first step prevents transaction senders from spending coins that do not exist, the second half of the first step prevents transaction senders from spending other people's coins, and the second step enforces conservation of value. In order to use this for payment, the protocol is as follows. Suppose Alice wants to send 11.7 BTC to Bob. First, Alice will look for a set of available UTXO that she owns that totals up to at least 11.7 BTC. Realistically, Alice will not be able to get exactly 11.7 BTC; say that the smallest she can get is 6+4+2=12. She then creates a transaction with those three inputs and two outputs. The first output will be 11.7 BTC with Bob's address as its owner, and the second output will be the remaining 0.3 BTC *change*, with the owner being Alice herself. Mining If we had access to a trustworthy centralized service, this system would be trivial to implement; it could simply be coded exactly as described, using a centralized server's hard drive to keep track of the state. However, with Bitcoin we are trying to build a decentralized currency system, so we will need to combine the state transaction system with a consensus system in order to ensure that everyone agrees on the order of transactions. Bitcoin's decentralized consensus process requires nodes in the network to continuously attempt to produce packages of transactions called *blocks*. The network is intended to produce roughly one block every ten minutes, with each block containing a timestamp, a nonce, a reference to (ie. hash of) the previous block and a list of all of the transactions that have taken place since the previous block. Over time, this creates a persistent, ever-growing, *blockchain* that constantly updates to represent the latest state of the Bitcoin ledger. The algorithm for checking if a block is valid, expressed in this paradigm, is as follows: Check if the previous block referenced by the block exists and is valid. Check that the timestamp of the block is greater than that of the previous blockfn2 and less than 2 hours into the future Check that the proof-of-work on the block is valid. Let S[0] be the state at the end of the previous block. Suppose TX is the block's transaction list with n transactions. For all i in 0...n-1, set S[i+1] = APPLY(S[i],TX[i]) If any application returns an error, exit and return false. Return true, and register S[n] as the state at the end of this block. Essentially, each transaction in the block must provide a valid state transition from what was the canonical state before the transaction was executed to some new state. Note that the state is not encoded in the block in any way; it is purely an abstraction to be remembered by the validating node and can only be (securely) computed for any block by starting from the genesis state and sequentially applying every transaction in every block. Additionally, note that the order in which the miner includes transactions into the block matters; if there are two transactions A and B in a block such that B spends a UTXO created by A, then the block will be valid if A comes before B but not otherwise. The one validity condition present in the above list that is not found in other systems is the requirement for *proof-of-work*. The precise condition is that the double-SHA256 hash of every block, treated as a 256-bit number, must be less than a dynamically adjusted target, which as of the time of this writing is approximately 2187. The purpose of this is to make block creation computationally *hard*, thereby preventing sybil attackers from remaking the entire blockchain in their favor. Because SHA256 is designed to be a completely unpredictable pseudorandom function, the only way to create a valid block is simply trial and error, repeatedly incrementing the nonce and seeing if the new hash matches. At the current target of ~2187, the network must make an average of ~269 tries before a valid block is found; in general, the target is recalibrated by the network every 2016 blocks so that on average a new block is produced by some node in the network every ten minutes. In order to compensate miners for this computational work, the miner of every block is entitled to include a transaction giving themselves 25 BTC out of nowhere. Additionally, if any transaction has a higher total denomination in its inputs than in its outputs, the difference also goes to the miner as a *transaction fee*. Incidentally, this is also the only mechanism by which BTC are issued; the genesis state contained no coins at all. In order to better understand the purpose of mining, let us examine what happens in the event of a malicious attacker. Since Bitcoin's underlying cryptography is known to be secure, the attacker will target the one part of the Bitcoin system that is not protected by cryptography directly: the order of transactions. The attacker's strategy is simple: Send 100 BTC to a merchant in exchange for some product (preferably a rapid-delivery digital good) ait for the delivery of the product Produce another transaction sending the same 100 BTC to himself Try to convince the network that his transaction to himself was the one that came first. Once step (1) has taken place, after a few minutes some miner will include the transaction in a block, say block number 270000. After about one hour, five more blocks will have been added to the chain after that block, with each of those blocks indirectly pointing to the transaction and thus *confirming* it. At this point, the merchant will accept the payment as finalized and deliver the product; since we are assuming this is a digital good, delivery is instant. Now, the attacker creates another transaction sending the 100 BTC to himself. If the attacker simply releases it into the wild, the transaction will not be processed; miners will attempt to run APPLY(S,TX) and notice that TX consumes a UTXO which is no longer in the state. So instead, the attacker creates a *fork* of the blockchain, starting by mining another version of block 270000 pointing to the same block 269999 as a parent but with the new transaction in place of the old one. Because the block data is different, this requires redoing the proof-of-work. Furthermore, the attacker's new version of block 270000 has a different hash, so the original blocks 270001 to 270005 do not *point* to it; thus, the original chain and the attacker's new chain are completely separate. The rule is that in a fork the longest blockchain is taken to be the truth, and so legitimate miners will work on the 270005 chain while the attacker alone is working on the 270000 chain. In order for the attacker to make his blockchain the longest, he would need to have more computational power than the rest of the network combined in order to catch up (hence, *51% attack*).
353
752
.
748
277
548
086
274
414
GENESIS
1
Chammy
0.
366
956
474
CHAMMY
3
DODO
0.
163
366
099
ДОДО
3
DOGE
0.
711
655
96
Ǝ⅁Oᗡ
2
DOPE
0.
741
811
384
DOPE
3
FEFE
0.
891
367
575
$FINEKILLER
3
FINE TOO
0.
494
823
990
374
118
332
FINE TOO
3
Furie Pets
315
758
.
234
715
162
FURIEPETS
1
GET IN LOSER
0.
747
467
792
UFO
3
Iggy The Iguana
0.
530
087
557
IGGY
3
Introduction to Bitcoin and Existing Concepts History The concept of decentralized digital currency, as well as alternative applications like property registries, has been around for decades. The anonymous e-cash protocols of the 1980s and the 1990s, mostly reliant on a cryptographic primitive known as Chaumian blinding, provided a currency with a high degree of privacy, but the protocols largely failed to gain traction because of their reliance on a centralized intermediary. In 1998, Wei Dai's b-money(opens in a new tab) became the first proposal to introduce the idea of creating money through solving computational puzzles as well as decentralized consensus, but the proposal was scant on details as to how decentralized consensus could actually be implemented. In 2005, Hal Finney introduced a concept of *reusable proofs of work(opens in a new tab)*, a system which uses ideas from b-money together with Adam Back's computationally difficult Hashcash puzzles to create a concept for a cryptocurrency, but once again fell short of the ideal by relying on trusted computing as a backend. In 2009, a decentralized currency was for the first time implemented in practice by Satoshi Nakamoto, combining established primitives for managing ownership through public key cryptography with a consensus algorithm for keeping track of who owns coins, known as *proof-of-work*. The mechanism behind proof-of-work was a breakthrough in the space because it simultaneously solved two problems. First, it provided a simple and moderately effective consensus algorithm, allowing nodes in the network to collectively agree on a set of canonical updates to the state of the Bitcoin ledger. Second, it provided a mechanism for allowing free entry into the consensus process, solving the political problem of deciding who gets to influence the consensus, while simultaneously preventing sybil attacks. It does this by substituting a formal barrier to participation, such as the requirement to be registered as a unique entity on a particular list, with an economic barrier - the weight of a single node in the consensus voting process is directly proportional to the computing power that the node brings. Since then, an alternative approach has been proposed called proof-of-stake, calculating the weight of a node as being proportional to its currency holdings and not computational resources; the discussion of the relative merits of the two approaches is beyond the scope of this paper but it should be noted that both approaches can be used to serve as the backbone of a cryptocurrency.
0.
835
101
982
209
472
656
GENESIS
2
MeV King
0.
782
224
200
284
762
996
MK
3
Not Pepe
0.
862
908
372
562
966
418
PEPE
2
OGFINE
0.
146
075
82
OGFINE
3
PEPE
0.
254
531
193
Пепе
2
Pepe 2.0
0.
353
808
746
Pepe 2.0
3
Pepe Bonk
118
996
048
626
.
846
321
266
PEBO
1
Pepe Classic
0.
822
831
886
732
101
457
PC
3
Pepe Is Fine
0.
604
210
638
PINE
3
PotatoGun
0.
717
602
644
POTATO
3
REAL PEPE FINE
0.
427
138
362
$RPF
3
Real Pineapple Owl
0.
544
308
398
дегенерация
2
SAME COIN
0.
285
529
001
SAME COIN
2
SHIFU
0.
397
656
455
SHIFU
3
SMURF on LSD
0.
962
354
256
СмурфЛСД
2
SMURFPEPE
0.
274
734
437
SPEPE
3
Schrödinger Cat
0.
821
937
055
737
144
921
Schrödinger
6
ScooBy Doo
1
497
599
.
110
019
898
ScooBy Doo
1
SirHiss
0.
288
838
491
HISS
3
Skull Kid
234.
133
812
933
SKULL
1
Sokoke Cat
0.
364
330
026
SOKOKE
3
TETE The Turtle
234
448
.
709
322
434
TETE
1
THEFINESTMEME
0.
262
785
611
FINEST
3
THIS IS SPARTA
1.
137
671
502
SPARTA
4
TOTO
0.
646
216
69
TOTO
3
The Iliad
0.
671
879
904
Iliad
2
WOJAK
0.
327
382
812
WOJAK
2
ƎԀƎԀ
0.
582
674
855
ƎԀƎԀ
2
ʞ∀ſOM
0.
430
335
055
ʞ∀ſOM
2
Сминемская монета
0.
716
124
455
SMINEM
3
∀N∀N∀q
0.
634
621
364
378
505
78
∀N∀N∀q
3
🇵 🇪 🇵 🇪
224
055
.
631
083
49
🇵 🇪 🇵 🇪
1
Transactions
All
Address on input side
Address on output side
Non-contract
Internal
A Next-Generation Smart Contract and Decentralized Application Platform Satoshi Nakamoto's development of Bitcoin in 2009 has often been hailed as a radical development in money and currency, being the first example of a digital asset which simultaneously has no backing or *intrinsic value(opens in a new tab)* and no centralized issuer or controller. However, another, arguably more important, part of the Bitcoin experiment is the underlying blockchain technology as a tool of distributed consensus, and attention is rapidly starting to shift to this other aspect of Bitcoin. Commonly cited alternative applications of blockchain technology include using on-blockchain digital assets to represent custom currencies and financial instruments (*colored coins(opens in a new tab)*), the ownership of an underlying physical device (*smart property(opens in a new tab)*), non-fungible assets such as domain names (*Namecoin(opens in a new tab)Ü), as well as more complex applications involving having digital assets being directly controlled by a piece of code implementing arbitrary rules (*smart contracts(opens in a new tab)*) or even blockchain-based *decentralized autonomous organizations(opens in a new tab)* (DAOs). What Ethereum intends to provide is a blockchain with a built-in fully fledged Turing-complete programming language that can be used to create *contracts* that can be used to encode arbitrary state transition functions, allowing users to create any of the systems described above, as well as many others that we have not yet imagined, simply by writing up the logic in a few lines of code. (ERC20)
AI SPIRAL (ERC20)
Along Came A Cat (ERC20)
Bitcoin As A State Transition System From a technical standpoint, the ledger of a cryptocurrency such as Bitcoin can be thought of as a state transition system, where there is a *state* consisting of the ownership status of all existing bitcoins and a *state transition function* that takes a state and a transaction and outputs a new state which is the result. In a standard banking system, for example, the state is a balance sheet, a transaction is a request to move $X from A to B, and the state transition function reduces the value in A's account by $X and increases the value in B's account by $X. If A's account has less than $X in the first place, the state transition function returns an error. Hence, one can formally define: The *state* in Bitcoin is the collection of all coins (technically, *unspent transaction outputs* or UTXO) that have been minted and not yet spent, with each UTXO having a denomination and an owner (defined by a 20-byte address which is essentially a cryptographic public keyfn1). A transaction contains one or more inputs, with each input containing a reference to an existing UTXO and a cryptographic signature produced by the private key associated with the owner's address, and one or more outputs, with each output containing a new UTXO to be added to the state. The state transition function APPLY(S,TX) -> S' can be defined roughly as follows: For each input in TX: If the referenced UTXO is not in S, return an error. If the provided signature does not match the owner of the UTXO, return an error. If the sum of the denominations of all input UTXO is less than the sum of the denominations of all output UTXO, return an error. Return S with all input UTXO removed and all output UTXO added The first half of the first step prevents transaction senders from spending coins that do not exist, the second half of the first step prevents transaction senders from spending other people's coins, and the second step enforces conservation of value. In order to use this for payment, the protocol is as follows. Suppose Alice wants to send 11.7 BTC to Bob. First, Alice will look for a set of available UTXO that she owns that totals up to at least 11.7 BTC. Realistically, Alice will not be able to get exactly 11.7 BTC; say that the smallest she can get is 6+4+2=12. She then creates a transaction with those three inputs and two outputs. The first output will be 11.7 BTC with Bob's address as its owner, and the second output will be the remaining 0.3 BTC *change*, with the owner being Alice herself. Mining If we had access to a trustworthy centralized service, this system would be trivial to implement; it could simply be coded exactly as described, using a centralized server's hard drive to keep track of the state. However, with Bitcoin we are trying to build a decentralized currency system, so we will need to combine the state transaction system with a consensus system in order to ensure that everyone agrees on the order of transactions. Bitcoin's decentralized consensus process requires nodes in the network to continuously attempt to produce packages of transactions called *blocks*. The network is intended to produce roughly one block every ten minutes, with each block containing a timestamp, a nonce, a reference to (ie. hash of) the previous block and a list of all of the transactions that have taken place since the previous block. Over time, this creates a persistent, ever-growing, *blockchain* that constantly updates to represent the latest state of the Bitcoin ledger. The algorithm for checking if a block is valid, expressed in this paradigm, is as follows: Check if the previous block referenced by the block exists and is valid. Check that the timestamp of the block is greater than that of the previous blockfn2 and less than 2 hours into the future Check that the proof-of-work on the block is valid. Let S[0] be the state at the end of the previous block. Suppose TX is the block's transaction list with n transactions. For all i in 0...n-1, set S[i+1] = APPLY(S[i],TX[i]) If any application returns an error, exit and return false. Return true, and register S[n] as the state at the end of this block. Essentially, each transaction in the block must provide a valid state transition from what was the canonical state before the transaction was executed to some new state. Note that the state is not encoded in the block in any way; it is purely an abstraction to be remembered by the validating node and can only be (securely) computed for any block by starting from the genesis state and sequentially applying every transaction in every block. Additionally, note that the order in which the miner includes transactions into the block matters; if there are two transactions A and B in a block such that B spends a UTXO created by A, then the block will be valid if A comes before B but not otherwise. The one validity condition present in the above list that is not found in other systems is the requirement for *proof-of-work*. The precise condition is that the double-SHA256 hash of every block, treated as a 256-bit number, must be less than a dynamically adjusted target, which as of the time of this writing is approximately 2187. The purpose of this is to make block creation computationally *hard*, thereby preventing sybil attackers from remaking the entire blockchain in their favor. Because SHA256 is designed to be a completely unpredictable pseudorandom function, the only way to create a valid block is simply trial and error, repeatedly incrementing the nonce and seeing if the new hash matches. At the current target of ~2187, the network must make an average of ~269 tries before a valid block is found; in general, the target is recalibrated by the network every 2016 blocks so that on average a new block is produced by some node in the network every ten minutes. In order to compensate miners for this computational work, the miner of every block is entitled to include a transaction giving themselves 25 BTC out of nowhere. Additionally, if any transaction has a higher total denomination in its inputs than in its outputs, the difference also goes to the miner as a *transaction fee*. Incidentally, this is also the only mechanism by which BTC are issued; the genesis state contained no coins at all. In order to better understand the purpose of mining, let us examine what happens in the event of a malicious attacker. Since Bitcoin's underlying cryptography is known to be secure, the attacker will target the one part of the Bitcoin system that is not protected by cryptography directly: the order of transactions. The attacker's strategy is simple: Send 100 BTC to a merchant in exchange for some product (preferably a rapid-delivery digital good) ait for the delivery of the product Produce another transaction sending the same 100 BTC to himself Try to convince the network that his transaction to himself was the one that came first. Once step (1) has taken place, after a few minutes some miner will include the transaction in a block, say block number 270000. After about one hour, five more blocks will have been added to the chain after that block, with each of those blocks indirectly pointing to the transaction and thus *confirming* it. At this point, the merchant will accept the payment as finalized and deliver the product; since we are assuming this is a digital good, delivery is instant. Now, the attacker creates another transaction sending the 100 BTC to himself. If the attacker simply releases it into the wild, the transaction will not be processed; miners will attempt to run APPLY(S,TX) and notice that TX consumes a UTXO which is no longer in the state. So instead, the attacker creates a *fork* of the blockchain, starting by mining another version of block 270000 pointing to the same block 269999 as a parent but with the new transaction in place of the old one. Because the block data is different, this requires redoing the proof-of-work. Furthermore, the attacker's new version of block 270000 has a different hash, so the original blocks 270001 to 270005 do not *point* to it; thus, the original chain and the attacker's new chain are completely separate. The rule is that in a fork the longest blockchain is taken to be the truth, and so legitimate miners will work on the 270005 chain while the attacker alone is working on the 270000 chain. In order for the attacker to make his blockchain the longest, he would need to have more computational power than the rest of the network combined in order to catch up (hence, *51% attack*). (ERC20)
Chammy (ERC20)
DODO (ERC20)
DOGE (ERC20)
DOPE (ERC20)
FEFE (ERC20)
FINE TOO (ERC20)
Furie Pets (ERC20)
GET IN LOSER (ERC20)
Iggy The Iguana (ERC20)
Introduction to Bitcoin and Existing Concepts History The concept of decentralized digital currency, as well as alternative applications like property registries, has been around for decades. The anonymous e-cash protocols of the 1980s and the 1990s, mostly reliant on a cryptographic primitive known as Chaumian blinding, provided a currency with a high degree of privacy, but the protocols largely failed to gain traction because of their reliance on a centralized intermediary. In 1998, Wei Dai's b-money(opens in a new tab) became the first proposal to introduce the idea of creating money through solving computational puzzles as well as decentralized consensus, but the proposal was scant on details as to how decentralized consensus could actually be implemented. In 2005, Hal Finney introduced a concept of *reusable proofs of work(opens in a new tab)*, a system which uses ideas from b-money together with Adam Back's computationally difficult Hashcash puzzles to create a concept for a cryptocurrency, but once again fell short of the ideal by relying on trusted computing as a backend. In 2009, a decentralized currency was for the first time implemented in practice by Satoshi Nakamoto, combining established primitives for managing ownership through public key cryptography with a consensus algorithm for keeping track of who owns coins, known as *proof-of-work*. The mechanism behind proof-of-work was a breakthrough in the space because it simultaneously solved two problems. First, it provided a simple and moderately effective consensus algorithm, allowing nodes in the network to collectively agree on a set of canonical updates to the state of the Bitcoin ledger. Second, it provided a mechanism for allowing free entry into the consensus process, solving the political problem of deciding who gets to influence the consensus, while simultaneously preventing sybil attacks. It does this by substituting a formal barrier to participation, such as the requirement to be registered as a unique entity on a particular list, with an economic barrier - the weight of a single node in the consensus voting process is directly proportional to the computing power that the node brings. Since then, an alternative approach has been proposed called proof-of-stake, calculating the weight of a node as being proportional to its currency holdings and not computational resources; the discussion of the relative merits of the two approaches is beyond the scope of this paper but it should be noted that both approaches can be used to serve as the backbone of a cryptocurrency. (ERC20)
MeV King (ERC20)
Not Pepe (ERC20)
OGFINE (ERC20)
PEPE (ERC20)
Pepe 2.0 (ERC20)
Pepe Bonk (ERC20)
Pepe Classic (ERC20)
Pepe Is Fine (ERC20)
PotatoGun (ERC20)
REAL PEPE FINE (ERC20)
Real Pineapple Owl (ERC20)
SAME COIN (ERC20)
SHIFU (ERC20)
SMURF on LSD (ERC20)
SMURFPEPE (ERC20)
Schrödinger Cat (ERC20)
ScooBy Doo (ERC20)
SirHiss (ERC20)
Skull Kid (ERC20)
Sokoke Cat (ERC20)
TETE The Turtle (ERC20)
THEFINESTMEME (ERC20)
THIS IS SPARTA (ERC20)
TOTO (ERC20)
The Iliad (ERC20)
WOJAK (ERC20)
ƎԀƎԀ (ERC20)
ʞ∀ſOM (ERC20)
Сминемская монета (ERC20)
∀N∀N∀q (ERC20)
🇵 🇪 🇵 🇪 (ERC20)
Previous
1
2
3
4
...
7
Next
0x3bd5fc4a412a1dbfd1a5c47b7c53e9aebf0ec75a75c2c4811306519eca592884
mined
245 days ago
Transfer
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x0c2b5fd1Fac9D960f40c820Ea11D9d16d0836F64
0.
033
917
206
978
520
311
ETH
0x78fcf65b19467f858f734dbfd85e80fbee58026b3716e4dfdfacbfa52a385927
mined
245 days 1 hour ago
0x095ea7b3
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x463E23918365404bbbaBC4DB0133650cdc242210
0 ETH
0x60029b602a493284e296b0169737d69364da47df35fad12f227e379d6ab23095
mined
245 days 1 hour ago
0xb6f9de95
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
02
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0xf9093bd09b2B545ba83C44243D194e65E6c22308
0.
02
WETH
0xf9093bd09b2B545ba83C44243D194e65E6c22308
0x463E23918365404bbbaBC4DB0133650cdc242210
2
368
.
168
781
034
TETE
0xf9093bd09b2B545ba83C44243D194e65E6c22308
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
234
448
.
709
322
434
TETE
0xce211bcb98798dab852abb102f902cca0aa489d9c35b8eb157d6e48cdbacc8c0
mined
245 days 2 hours ago
0x791ac947
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0 ETH
ERC20 Token Transfers
0x3fd038745Ef9189509c81F7A439f335B98dCCdcC
0x30A91C51913549e9a178d577338aeE00A5Bdb586
1
680
028
300
391
WOJAK
0x30A91C51913549e9a178d577338aeE00A5Bdb586
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
039
145
752
115
869
086
WETH
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x30A91C51913549e9a178d577338aeE00A5Bdb586
1
680
028
300
391
WOJAK
0x30A91C51913549e9a178d577338aeE00A5Bdb586
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
037
820
081
387
673
254
WETH
0x38e9819e89b7df9a204c3573dfc0397658edd1ded6f8d0ceddf38ede69438e24
mined
245 days 2 hours ago
0x095ea7b3
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x3fd038745Ef9189509c81F7A439f335B98dCCdcC
0 ETH
0x5e67c8a06f78081741814ebec72f7804862cba287b3ea734c331b6f5b4b5bbc7
mined
245 days 2 hours ago
0xfb3bdb41
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
016
546
612
059
387
386
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0x30A91C51913549e9a178d577338aeE00A5Bdb586
0.
009
411
108
461
226
449
WETH
0x30A91C51913549e9a178d577338aeE00A5Bdb586
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
1
680
028
300
391
.
327
382
812
WOJAK
0xbadb8fdb0bd51ee16bd334f54d7ad90863d1b0acfb35fe3ee7eab024d830320e
mined
245 days 2 hours ago
0x095ea7b3
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0xa15257bC20F6a02BBA818A01D91AFE8C00bAABf2
0 ETH
0x25eddbf0908f7a72f527e4d7a34f70c4054bea01c4b42f1159e6e32cd0c532dd
mined
245 days 2 hours ago
0xfb3bdb41
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
018
492
643
421
527
04
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0xF1cb45b452A8B0774bB59ec20D07f2Eb6c147F55
0.
009
246
321
710
763
52
WETH
0xF1cb45b452A8B0774bB59ec20D07f2Eb6c147F55
0xa15257bC20F6a02BBA818A01D91AFE8C00bAABf2
499
199
.
703
339
965
ScooBy Doo
0xF1cb45b452A8B0774bB59ec20D07f2Eb6c147F55
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
1
497
599
.
110
019
898
ScooBy Doo
0xcd191b2ddbe6dc7eea19bf99e4fde5733b64f1c9baeee2a4dda1408172766ad3
mined
245 days 6 hours ago
0x791ac947
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0 ETH
ERC20 Token Transfers
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0xeD820452f4a78Ce7EEb14324Eeb1C6cb40ca49f2
3
190
.
44
CHAMMY
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x105a1DF43cc0716c00521F5671EbAE9ffC63C9B6
315
853
.
56
CHAMMY
0x105a1DF43cc0716c00521F5671EbAE9ffC63C9B6
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
004
382
698
108
079
058
WETH
0xbde10ff130f56575017902f1ed2a2e46ef0ff347c7270b0c85063e55442edf39
mined
245 days 7 hours ago
0x095ea7b3
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0xeD820452f4a78Ce7EEb14324Eeb1C6cb40ca49f2
0 ETH
0x0402f37452e229034d0ec8e4574b1d8009eca7c5058a9694b3e660da67ced1e2
mined
245 days 7 hours ago
0xb6f9de95
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
02
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0x105a1DF43cc0716c00521F5671EbAE9ffC63C9B6
0.
02
WETH
0x105a1DF43cc0716c00521F5671EbAE9ffC63C9B6
0xeD820452f4a78Ce7EEb14324Eeb1C6cb40ca49f2
3
222
.
670
373
297
CHAMMY
0x105a1DF43cc0716c00521F5671EbAE9ffC63C9B6
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
319
044
.
366
956
474
CHAMMY
0x5b67cf7f32bedd146d46f6f6c368455619d2ca2736b6efc3ed36eb8ef74d4070
mined
245 days 9 hours ago
Transfer
0x6202F39eFf94798A206950F6fBFfafeD9102c987
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0.
03
ETH
0x010d9214b267260fa04a9b4f19dc91feade81edcb7daf01c4584e4ed21ef8e37
mined
245 days 9 hours ago
Transfer
0xDFd5293D8e347dFe59E90eFd55b2956a1343963d
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0.
049
47
ETH
0xc2effcdfad15f175852a933b911d5463c8775bb946133083965d7398b87c232d
mined
245 days 12 hours ago
0x095ea7b3
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0xA0eA6a7f6bFbD5E9daE21717FFc2638C3E7356Ed
0 ETH
0xfd910f68cba351483392783394f2ea28d9adffa38bf96ee44f25ada9814a986a
mined
245 days 12 hours ago
0xb6f9de95
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
04
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0x47A888a587F2C26A5aE18d68f9397a471EACd906
0.
04
WETH
0x47A888a587F2C26A5aE18d68f9397a471EACd906
0xA0eA6a7f6bFbD5E9daE21717FFc2638C3E7356Ed
1
201
980
289
.
160
063
851
PEBO
0x47A888a587F2C26A5aE18d68f9397a471EACd906
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
118
996
048
626
.
846
321
266
PEBO
0xb63c7b6b32c1561ec1c80b9a7430be313863cead1bf275f58fe96797c2595037
mined
245 days 22 hours ago
0x791ac947
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0 ETH
ERC20 Token Transfers
0x6460ADFe59B5b409487c5fC96B14B59E3646a127
0xAA57E2A49D37aCA3075e965C2C891495Ff19736b
268
827
.
428
088
517
648
892
143
CAT
0xAA57E2A49D37aCA3075e965C2C891495Ff19736b
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
003
454
767
099
495
334
WETH
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x6460ADFe59B5b409487c5fC96B14B59E3646a127
41
173
.
04
CAT
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0xAA57E2A49D37aCA3075e965C2C891495Ff19736b
2
017
478
.
96
CAT
0xAA57E2A49D37aCA3075e965C2C891495Ff19736b
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
025
597
622
535
360
181
WETH
0xf1ef6b1b99ed141ebb6fddb7deedf7eec73d6e3f98340a0cdf72ae40680681a7
mined
245 days 23 hours ago
0x095ea7b3
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x6460ADFe59B5b409487c5fC96B14B59E3646a127
0 ETH
0xc7c34ef83c47cd6405c74d867b22d6eddd47076629dd875d916c8f3192552fd3
mined
245 days 23 hours ago
0xb6f9de95
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
02
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0xAA57E2A49D37aCA3075e965C2C891495Ff19736b
0.
02
WETH
0xAA57E2A49D37aCA3075e965C2C891495Ff19736b
0x6460ADFe59B5b409487c5fC96B14B59E3646a127
514
663
.
107
857
793
500
827
259
CAT
0xAA57E2A49D37aCA3075e965C2C891495Ff19736b
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
2
058
652
.
431
431
174
003
309
04
CAT
0x984520014bd7a7eb98b1f4368f00b3149013c31fd70dbfd67e7c7b0c69f0a485
mined
246 days 1 hour ago
Transfer
0xDFd5293D8e347dFe59E90eFd55b2956a1343963d
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0.
039
47
ETH
0x99e16144d31257beb5fbe6795c9d9fdd2602b62714220f230fca84e7c42e9d7c
mined
246 days 1 hour ago
0x095ea7b3
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0xAd29c18d6DAB03fA048549E4e5EB232578C6f2DF
0 ETH
0xdec92e35cc03b0e97a2e618370ff089a4dee8c7ab5360970ca11ca95d3b40627
mined
246 days 1 hour ago
0xb6f9de95
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
02
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0xD68163cb8AE93D0cB4f5650dc9418C2e22FEa140
0.
02
WETH
0xD68163cb8AE93D0cB4f5650dc9418C2e22FEa140
0xAd29c18d6DAB03fA048549E4e5EB232578C6f2DF
2
263
.
188
192
762
🇵 🇪 🇵 🇪
0xD68163cb8AE93D0cB4f5650dc9418C2e22FEa140
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
224
055
.
631
083
49
🇵 🇪 🇵 🇪
0x0d1fda5ea1d51017591bde801385bef4598c9aa6df22eb56bb06ba929b728e8b
mined
246 days 1 hour ago
0x791ac947
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0 ETH
ERC20 Token Transfers
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x12b1CF39A893f4304533daC8ba771a03Ef8c9872
44
754
.
6
MK
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0xdDee144d6f652F0F25BE43577DD655cB6da4E753
850
337
.
4
MK
0xdDee144d6f652F0F25BE43577DD655cB6da4E753
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
013
452
319
371
658
029
WETH
0x65ed550cd2fa1d205aa07620d7c24db3b27cfa96429574404837bae1a6ed7bb6
mined
246 days 2 hours ago
0x095ea7b3
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x12b1CF39A893f4304533daC8ba771a03Ef8c9872
0 ETH
0x7c28c19ed0497d99aa7c52ab58d02e93638dc7a67f873c32eb9a9a7bb5920cdc
mined
246 days 2 hours ago
0xb6f9de95
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
02
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0xdDee144d6f652F0F25BE43577DD655cB6da4E753
0.
02
WETH
0xdDee144d6f652F0F25BE43577DD655cB6da4E753
0x12b1CF39A893f4304533daC8ba771a03Ef8c9872
223
773
.
195
556
050
071
190
749
MK
0xdDee144d6f652F0F25BE43577DD655cB6da4E753
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
895
092
.
782
224
200
284
762
996
MK
0xf3f77c4e53c0d8400cff5172fced303e717e89d3942975acfc7612e002b23f4b
mined
246 days 8 hours ago
0x791ac947
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0 ETH
ERC20 Token Transfers
0x00709Ecf38Ff96b99c41f4c5eCC43177aed66f4e
0xcc88B675De7BeA6B743467808e7b81C6330Caf0E
12
140
993
525
Пепе
0xcc88B675De7BeA6B743467808e7b81C6330Caf0E
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
003
565
478
568
981
89
WETH
Previous
1
2
3
4
...
7
Next