Ethereum Explorer
Blocks
Status
Address
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0.
000
163
674
582
729
ETH
Confirmed
Balance
0.
000
163
674
582
729
ETH
Transactions
182
Non-contract Transactions
175
Internal Transactions
0
Nonce
159
ERC20 Tokens
40
Contract
Quantity
Value
Transfers
#
$ HEXPool.io
93
588
.
75
wHEX
1
AUTO DIP BUYER
2
009
564
.
624
865
961
EATDIP
1
Amino
0 AMO
2
AnonSwap.me
0 ANON
3
BLUE
0 BLUE
2
BONE SHIBASWAP
0 BONE
9
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*).
347
862
.
428
332
412
786
195
899
GENESIS
1
Borat Token
0 BORAT
2
Golden Ticket
15
213
069
.
103
768
983
TICKET
1
Golden Ticket
1
217
419
.
065
245
257
TICKET
1
GrayBot
16
000
GB
1
HarryPotterObamaMario9INU
0 ERC20
3
HaryyPotheadHermoineGanjaRonWeedlyHashgridAlkushDumbledoreSeverusVape
0 POT
3
Infernium
0 BURN
3
Juice Staking
0 JUICE
3
Knife
693
497
.
787
363
426
729
947
086
SWISS
1
LENNY FACE
0 ( ͡° ͜ʖ ͡°)
5
Lil Mayo
0 MAYO
3
Marvin the Paranoid Android
0 MARVIN
2
Metis Token
0 Metis
4
MichaelJacksonTrumpNarcosFortnite777DoxInu
0 LTC
3
Pixel Cloud
2
684
.
954
094
928
PXC
1
SHIA
0 SHIA
2
SNEK
0 SNEK
3
SendIt
3
069
800
.
031
731
245
609
161
631
$SEND
1
SharesBot
0 SB
5
SharesBot
16
000
SB
1
Sonicisbroke0dollars
0 BRUCELEE
2
Tether USD
0 USDT
6
The Great Sprint
0 Sprint
3
The Intern
0 INT
2
This world is messed up. I have no desire left, and the only way to escape from this demoralized society is to become wealthy. People sexually identify as objects, wars and unrest are simmering worldwide, and women nowadays behave like alpha animals. Welfare states allow people to vegetate in a gilded cage, also known as a mouse paradise, increasingly harmonizing with their slave driver, also known as the government, as if in Stockholm syndrome. The family image is destroyed, moral values are worth nothing anymore. I despise the idea of the dollar's Ponzi scheme, but those who don't participate go hungry. Did you ever heard of the Universe25? The Universe 25 experiment was a study conducted by John B. Calhoun in the 1970s. It involved creating an enclosed environment for laboratory mice, providing them with unlimited resources like food and water, and monitoring their behavior as the population grew. The goal was to study the effects of overpopulation and resource depletion on social behavior and population dynamics. The experiment resulted in the emergence of various unusual and dysfunctional behaviors among the mice, such as increased aggression, withdrawal from social interactions, and the eventual collapse of the population, despite the availability of resources. It's often cited in discussions about the potential consequences of overpopulation and social breakdown in confined spaces, and it has been used as a metaphor for understanding the challenges of overcrowding and limited resources in human societies. What does this experiment prove? That the wrong kind of security can rob us of the true security of freedom and creativity. I won't let this be taken from me, and I'll fight against being a part of this messed-up system. How? Well, with creativity. I've delved into the world of decentralized finance as a developer to create what are called Memes with the goal of feeding everyone from my simmering hotpot. It's the only path to true freedom. I've had enough of being morally exploited, and with this SHITCOIN, I'll make a name for myself. Forget all those rug pulls by crypto addicts from Somalia Jeets who try to snatch your ETH with cheap projects. We're forging our own utopia of freedom, the utopia of memes. Are we mice or unique individuals with hopes and dreams? Let's spread the word and achieve prosperity together. This is the beginning of a financial resistance revolution. We're creating our own paradise.
22
067
.
874
864
167
PARADISE
1
Type On Chain
1
284
.
545
868
447
TYPE
1
Uni01cinoSamabOrettoPyrraH
0 ǝdǝd
3
Victoria VR
0 VR
2
Welcome Back To ETH
5
881
670
.
974
839
619
welcome
1
gmeow Coin
0 gmeow
3
sooooooooooooooooooooooooooooooooooooooooooooooo
0 sooooooooooooooooooooooooooooooooooooooooooooooo
3
spurdo
0 spurdo
3
uhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
0 uhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
3
Transactions
All
Address on input side
Address on output side
Non-contract
Internal
$ HEXPool.io (ERC20)
AUTO DIP BUYER (ERC20)
Amino (ERC20)
AnonSwap.me (ERC20)
BLUE (ERC20)
BONE SHIBASWAP (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)
Borat Token (ERC20)
Golden Ticket (ERC20)
Golden Ticket (ERC20)
GrayBot (ERC20)
HarryPotterObamaMario9INU (ERC20)
HaryyPotheadHermoineGanjaRonWeedlyHashgridAlkushDumbledoreSeverusVape (ERC20)
Infernium (ERC20)
Juice Staking (ERC20)
Knife (ERC20)
LENNY FACE (ERC20)
Lil Mayo (ERC20)
Marvin the Paranoid Android (ERC20)
Metis Token (ERC20)
MichaelJacksonTrumpNarcosFortnite777DoxInu (ERC20)
Pixel Cloud (ERC20)
SHIA (ERC20)
SNEK (ERC20)
SendIt (ERC20)
SharesBot (ERC20)
SharesBot (ERC20)
Sonicisbroke0dollars (ERC20)
Tether USD (ERC20)
The Great Sprint (ERC20)
The Intern (ERC20)
This world is messed up. I have no desire left, and the only way to escape from this demoralized society is to become wealthy. People sexually identify as objects, wars and unrest are simmering worldwide, and women nowadays behave like alpha animals. Welfare states allow people to vegetate in a gilded cage, also known as a mouse paradise, increasingly harmonizing with their slave driver, also known as the government, as if in Stockholm syndrome. The family image is destroyed, moral values are worth nothing anymore. I despise the idea of the dollar's Ponzi scheme, but those who don't participate go hungry. Did you ever heard of the Universe25? The Universe 25 experiment was a study conducted by John B. Calhoun in the 1970s. It involved creating an enclosed environment for laboratory mice, providing them with unlimited resources like food and water, and monitoring their behavior as the population grew. The goal was to study the effects of overpopulation and resource depletion on social behavior and population dynamics. The experiment resulted in the emergence of various unusual and dysfunctional behaviors among the mice, such as increased aggression, withdrawal from social interactions, and the eventual collapse of the population, despite the availability of resources. It's often cited in discussions about the potential consequences of overpopulation and social breakdown in confined spaces, and it has been used as a metaphor for understanding the challenges of overcrowding and limited resources in human societies. What does this experiment prove? That the wrong kind of security can rob us of the true security of freedom and creativity. I won't let this be taken from me, and I'll fight against being a part of this messed-up system. How? Well, with creativity. I've delved into the world of decentralized finance as a developer to create what are called Memes with the goal of feeding everyone from my simmering hotpot. It's the only path to true freedom. I've had enough of being morally exploited, and with this SHITCOIN, I'll make a name for myself. Forget all those rug pulls by crypto addicts from Somalia Jeets who try to snatch your ETH with cheap projects. We're forging our own utopia of freedom, the utopia of memes. Are we mice or unique individuals with hopes and dreams? Let's spread the word and achieve prosperity together. This is the beginning of a financial resistance revolution. We're creating our own paradise. (ERC20)
Type On Chain (ERC20)
Uni01cinoSamabOrettoPyrraH (ERC20)
Victoria VR (ERC20)
Welcome Back To ETH (ERC20)
gmeow Coin (ERC20)
sooooooooooooooooooooooooooooooooooooooooooooooo (ERC20)
spurdo (ERC20)
uhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh (ERC20)
Previous
1
2
3
4
...
8
Next
0xf644d27feda7d051a800f1e76b2c5fcfe344f334709fa25a78805746fbdf5095
mined
54 days ago
Transfer
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x2F0e848615D79E401EF6601aa4Ee38Af73ff2300
1 ETH
0xddf4a780ef94ea56c4aa6e680297d1b34e829e7e42f9ebe1765f227123357f82
mined
54 days ago
0x3593564c
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD
0 ETH
ERC20 Token Transfers
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x4085cAFb2c519e6bf69Ad410d91dbb6139948366
17
282
.
577
266
893
657
285
092
VR
0x4085cAFb2c519e6bf69Ad410d91dbb6139948366
0x0d4a11d5EEaaC28EC3F61d100daF4d40471f1852
576.
180
189
USDT
0x0d4a11d5EEaaC28EC3F61d100daF4d40471f1852
0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD
0.
145
817
270
360
895
346
WETH
0xd72406dd1bbb94ce3b663813a27d49cc4b0df2b0ffeee7556ca9887ec00ab427
mined
54 days ago
0x3593564c
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD
0 ETH
ERC20 Token Transfers
0xC1B24a9ecf68C14fFe65263b1591C29dD341D09d
0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD
0.
034
145
817
614
087
328
WETH
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0xC1B24a9ecf68C14fFe65263b1591C29dD341D09d
100
108
.
866
482
182
428
777
584
AMO
0xefd8bab6747a0e73cc78fa98cd268f12f52d0be71a49dd9a4ae882280b79c2cd
mined
56 days 23 hours ago
0xba1f77e8
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x5F6AE08B8AeB7078cf2F96AFb089D7c9f51DA47d
0 ETH
ERC20 Token Transfers
0x5F6AE08B8AeB7078cf2F96AFb089D7c9f51DA47d
0x98078db053902644191f93988341E31289E1C8FE
0.
700
549
559
908
649
601
stETH
0xb44b68a6edd381d945b453beebe9e0ee979dc05fe62fda86cd89596a43f7c417
mined
63 days 19 hours ago
Transfer
0x2F0e848615D79E401EF6601aa4Ee38Af73ff2300
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
1 ETH
0x0d05c031be1c7bba5479ad21d0d158d69e655c05d3adad7f8a3a9d03bd39072e
mined
63 days 19 hours ago
Failed
Transfer
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x697402166Fbf2F22E970df8a6486Ef171dbfc524
0.
1
ETH
0xbf23711505dfe4345ce965edad4b06621f125878dcd1cbdc0410727e7ba9b1ef
mined
63 days 22 hours ago
Transfer
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x697402166Fbf2F22E970df8a6486Ef171dbfc524
0.
1
ETH
0xbb16f846a018b3c089fb89e7746483b88c2d962f915b2724f69a28305ad8b29d
mined
65 days 19 hours ago
0x095ea7b3
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x1a2EB478FA07125C9935A77b3C03a82470801E30
0 ETH
0xa2ce2dec647a941a6147c26d80830d4e97b20435d3a30eccfe66b5be83c6f8c2
mined
65 days 19 hours ago
0xf6326fb3
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x5F6AE08B8AeB7078cf2F96AFb089D7c9f51DA47d
0.
7
ETH
0x12ef483501f8326b8e775fc23327d75510f59564d7396aba57a9b3cce6896099
mined
77 days 16 hours ago
Transfer
0x2F0e848615D79E401EF6601aa4Ee38Af73ff2300
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
1 ETH
0xe8e41b88fab872617122afaaa77b250f612c068f50890c583b3b12f2f06aeb7d
mined
83 days 19 hours ago
0x095ea7b3
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x7d5121505149065b562C789A0145eD750e6E8cdD
0 ETH
0x1dc3dc6229b7966fc706a495a84e036d42e742771fba5ce0483e17148f301bdd
mined
83 days 19 hours ago
Transfer
0x9f1842a615a14BCe5723f4C5019D6f67c889B632
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0.
015
885
334
497
241
998
ETH
0xfed50b52d4c1bda1ac20e98bb1d0b2c87e216b34a2c10fa2088d4b2c1d8f7f6b
mined
83 days 19 hours ago
Transfer
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0.
013
641
009
764
641
676
ETH
0xe0934888ee56e23169d9bfacc3050276a4fa1e0a716afbda7ae39501ad7e340e
mined
83 days 19 hours ago
Transfer
0x5795fDBDB962B8CbeFAAf4564904b2A554897Ae8
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0.
011
337
571
220
932
337
ETH
0xb247af55a146cd43314b36c374982a120b480a9d0d00a01e704dd916618ce869
mined
91 days 3 hours ago
Transfer
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x5795fDBDB962B8CbeFAAf4564904b2A554897Ae8
0.
013
ETH
0xfccfb564a274fa653fca799ad56bd3775d1c0a7a33fe81216aecf6ab75a30e0f
mined
92 days 2 hours ago
0x8e0f8e7e
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x70e967acFcC17c3941E87562161406d41676FD83
0.
08
ETH
0xd6c5e578138872982325f3fe6cd4a65f68fe358826ebea9d84e7be73c448ea38
mined
124 days 17 hours ago
Transfer
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x27D622fB7c62f3CF2b5A081836D41Aa168d3c01e
0.
1
ETH
0x04ac9e507539bcc5f0c80460fb3c4e12723d467566365159b7e54c18c51110ca
mined
124 days 17 hours ago
Transfer
0x27D622fB7c62f3CF2b5A081836D41Aa168d3c01e
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0.
1
ETH
0x15a79f5a498a41d0cc09f90662f8814042fc42c9c9a428b5e02c86ada2652985
mined
125 days 20 hours ago
0x3593564c
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD
0.
2
ETH
ERC20 Token Transfers
0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD
0x0d4a11d5EEaaC28EC3F61d100daF4d40471f1852
0.
2
WETH
0x0d4a11d5EEaaC28EC3F61d100daF4d40471f1852
0x4085cAFb2c519e6bf69Ad410d91dbb6139948366
472.
352
562
USDT
0x4085cAFb2c519e6bf69Ad410d91dbb6139948366
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
17
282
.
577
266
893
657
285
092
VR
0xd141358ef79c798ff68b1c1396d164803968ea815320906e1eb8258557a1a453
mined
127 days 13 hours ago
0x9fbf10fc
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x8731d54E9D02c286767d56ac03e8037C07e01e98
0.
000
739
243
310
421
033
ETH
ERC20 Token Transfers
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0xd8772edBF88bBa2667ed011542343b0eDDaCDa47
3.
162
410
167
447
949
666
Metis
0x6290f3733118571e06ff8e40e459c06a12828e8d8f44f3f72650fed853b50055
mined
127 days 13 hours ago
0x095ea7b3
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x9E32b13ce7f2E80A01932B42553652E053D6ed8e
0 ETH
0x28ce037422100a5be1d541179f2c7bc4495161ee591f3f943baea38f8f0b20b3
mined
127 days 13 hours ago
0x3593564c
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD
0 ETH
ERC20 Token Transfers
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x0d4a11d5EEaaC28EC3F61d100daF4d40471f1852
295.
278
22
USDT
0x0d4a11d5EEaaC28EC3F61d100daF4d40471f1852
0xd03dffD02Db4B076e3eeD9272a6A243a23DE16e3
0.
124
982
134
436
188
151
WETH
0xd03dffD02Db4B076e3eeD9272a6A243a23DE16e3
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
3.
162
410
167
447
949
666
Metis
0x3db1a2ecbae3858816a727f53f9fcb0f0a7124b411bb7776ba7caf119a683532
mined
127 days 13 hours ago
0x095ea7b3
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0xdAC17F958D2ee523a2206206994597C13D831ec7
0 ETH
0xaea4df03dd578ec5370c5132eb98f6e013f3137f858183012cde565e8eebd1a0
mined
127 days 22 hours ago
0x3593564c
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD
0 ETH
ERC20 Token Transfers
0x1c98562A2FaB5aF19D8Fb3291a36AC3C618835D9
0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD
0.
129
204
889
382
341
532
WETH
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x1c98562A2FaB5aF19D8Fb3291a36AC3C618835D9
3.
297
512
490
543
073
023
Metis
0x11b815efB8f581194ae79006d24E0d814B7697F6
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
295.
278
22
USDT
0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD
0x11b815efB8f581194ae79006d24E0d814B7697F6
0.
129
204
889
382
341
532
WETH
0xa542eb55b735f6e6b63133357f9842ca61804b7269ad00ccac221137a151f76b
mined
127 days 22 hours ago
0x095ea7b3
0x0630a99B57ce5dC3210870E6581e0f17f0f29E1C
0x9E32b13ce7f2E80A01932B42553652E053D6ed8e
0 ETH
Previous
1
2
3
4
...
8
Next