Ethereum Explorer
Blocks
Status
Address
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0.
000
203
977
998
168
ETH
Confirmed
Balance
0.
000
203
977
998
168
ETH
Transactions
21
Non-contract Transactions
21
Internal Transactions
0
Nonce
20
ERC20 Tokens
6
Contract
Quantity
Value
Transfers
#
BURN
0.
143
021
850
322
877
192
BURN
4
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*).
355
601
.
490
261
159
221
191
407
GENESIS
1
GOPNIK
3
080
761
.
493
588
985
гопник
1
NO PROBLEMO
0.
275
911
734
NOPROBLEMO
3
Schrodinger
0.
986
993
749
585
388
011
Dinger
3
TAROMARU
334
393
.
265
190
015
SHIBA
1
Transactions
All
Address on input side
Address on output side
Non-contract
Internal
BURN (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)
GOPNIK (ERC20)
NO PROBLEMO (ERC20)
Schrodinger (ERC20)
TAROMARU (ERC20)
0x8d6844c02e2608da16ba4176f24cfacc0c0da54d461d99cfd00e64839ef6a764
mined
255 days 5 hours ago
Transfer
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x93fA6126a82bF203B59fc1A6865BCF0c59763928
0.
015
315
272
089
888
979
ETH
0x91dfb66e33848fd9aaf034b7110f074c482b18cfe53919fe44cf6cb705bf35f2
mined
255 days 7 hours ago
Failed
0x791ac947
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0 ETH
0x911d8aa7833032787a2c8dc29c4ce10270b6ec3667c707626a1f659a7db86971
mined
255 days 8 hours ago
0x095ea7b3
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0xa291aCAf4a8fE16A5b1F15c6d6004fa3aB7f58ca
0 ETH
0x74ef48eb51cf4019def7a7c9ae2a9bb8a3d308b7eb8bff4c697124d4a1459191
mined
255 days 8 hours ago
0xfb3bdb41
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
010
128
725
048
277
484
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0xcF04dE43F727369B68acf4062e257005018a7608
0.
005
330
907
920
146
044
WETH
0xcF04dE43F727369B68acf4062e257005018a7608
0xa291aCAf4a8fE16A5b1F15c6d6004fa3aB7f58ca
3
591
.
934
245
062
214
355
468
GENESIS
0xcF04dE43F727369B68acf4062e257005018a7608
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
355
601
.
490
261
159
221
191
407
GENESIS
0xb8cf92c65dffedebe1936f13e119170bc7478c0caf996a2c7e473785eeec3f33
mined
255 days 9 hours ago
0x095ea7b3
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x97421F52B29f190eF32DC8A27E8843B8B3F1e6AD
0 ETH
0xd34c905420b7f7f421cde8b9fbf3c0d7e45616e2292ebe61097418afe955338e
mined
255 days 9 hours ago
0xb6f9de95
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
05
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0x91912626A96dD022Ee9694621801CA51C4221B52
0.
05
WETH
0x91912626A96dD022Ee9694621801CA51C4221B52
0x97421F52B29f190eF32DC8A27E8843B8B3F1e6AD
3
377
.
709
749
394
SHIBA
0x91912626A96dD022Ee9694621801CA51C4221B52
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
334
393
.
265
190
015
SHIBA
0xf381d3f0d1bde352e06569d04415ba3d9268bbc221a8daf8e73e7d4eceed1f5a
mined
255 days 9 hours ago
0x791ac947
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0 ETH
ERC20 Token Transfers
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x62f0A25F884Cc9BF186196Cc1cAE15A58FcE4732
30
945
813
562
Dinger
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0xcd145189A12CCc3F9c622766fb20D00dc2059eAd
0 Dinger
0x62f0A25F884Cc9BF186196Cc1cAE15A58FcE4732
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
052
854
226
762
082
064
WETH
0x62ceb3deeac9b1502a27229a4739be040a76821c82615871fd184113c4c91f05
mined
255 days 10 hours ago
0x095ea7b3
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0xcd145189A12CCc3F9c622766fb20D00dc2059eAd
0 ETH
0xe756a8f3d58cd187fbc0d24dde9e49daafb2fd08953c47fcad51d166bb4fb23b
mined
255 days 10 hours ago
0xb6f9de95
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
05
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0x62f0A25F884Cc9BF186196Cc1cAE15A58FcE4732
0.
05
WETH
0x62f0A25F884Cc9BF186196Cc1cAE15A58FcE4732
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
30
945
813
562
.
986
993
749
585
388
011
Dinger
0x62f0A25F884Cc9BF186196Cc1cAE15A58FcE4732
0xcd145189A12CCc3F9c622766fb20D00dc2059eAd
0 Dinger
0xe83a05188ef1d5b5a64290b6d4acbcf91fa04f32e4e81df9e46781ea7a9638d7
mined
255 days 20 hours ago
0x791ac947
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0 ETH
ERC20 Token Transfers
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x0dd8F9B1A1691e639Ebd21B7416EE6E7ebBec504
7
436
.
46
NOPROBLEMO
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x6ac48E6B64f815c2E4d4dd7E924bb7be757D0215
736
209
.
54
NOPROBLEMO
0x6ac48E6B64f815c2E4d4dd7E924bb7be757D0215
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
037
185
630
361
484
355
WETH
0xee4abf7694ae82f4f4feda3eab998b3d4db5c62df0ca72b592a914267fe4bfdc
mined
255 days 20 hours ago
Transfer
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0xCac0F1A06D3f02397Cfb6D7077321d73b504916e
0.
01
ETH
0x4575f61be014a95acb4f30f4cab9c67f547ef532ed09cdb44cd962f6bf8972c3
mined
255 days 20 hours ago
0x095ea7b3
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x0dd8F9B1A1691e639Ebd21B7416EE6E7ebBec504
0 ETH
0xdfbe40caed0e894baaa835fd3ebe05f92871643ba3fc2763cf4b187ed436df21
mined
255 days 20 hours ago
0xb6f9de95
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
05
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0x6ac48E6B64f815c2E4d4dd7E924bb7be757D0215
0.
05
WETH
0x6ac48E6B64f815c2E4d4dd7E924bb7be757D0215
0x0dd8F9B1A1691e639Ebd21B7416EE6E7ebBec504
7
511
.
578
544
562
NOPROBLEMO
0x6ac48E6B64f815c2E4d4dd7E924bb7be757D0215
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
743
646
.
275
911
734
NOPROBLEMO
0x1a01c4aa77d7acd489ec2ec4b7d7ce145073a3dbdcad7c4d3b29550e249a3b25
mined
255 days 20 hours ago
Failed
0x791ac947
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0 ETH
0x2506c2563bca555e1b064940c00f4d4e1283c192a895551d323377ebe9cc6cdc
mined
255 days 20 hours ago
0x095ea7b3
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0xcf91a0a04631A1857285E1c53bb48CD14B48AD20
0 ETH
0x86a17172405e36138f479d794d44ddb41be51723fe264dcb2c3d92677b23de5b
mined
255 days 20 hours ago
0xb6f9de95
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
05
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0x8324611D7c7276B0F2f939E07A5Efad24e854795
0.
05
WETH
0x8324611D7c7276B0F2f939E07A5Efad24e854795
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
3
080
761
.
493
588
985
гопник
0x2f60d5b436d931e4a164fe2ef6b697db79735b2d131fea003f29cda4b2476285
mined
255 days 20 hours ago
Failed
0xfb3bdb41
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
030
782
030
433
353
13
ETH
0x065ad1305a8d746ad46ffaae38368c7026011bd9db1346ee023471dbd570e041
mined
255 days 21 hours ago
0x791ac947
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0 ETH
ERC20 Token Transfers
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x0000000000000000000000000000000000000000
1
340
048
374
.
61
BURN
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0xa8b312c331e3eDaDc91Be427e3a9c06Cf135736B
10
720
386
996
.
88
BURN
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x07293300B92b3DF15F1772f777aF1756fc73A03B
255
949
239
550
.
51
BURN
0x07293300B92b3DF15F1772f777aF1756fc73A03B
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
058
507
287
944
109
51
WETH
0xc9e6789dec670170e84cce40988893ac6e3676f0d2bc0e3e56f6a38637b22f2c
mined
255 days 21 hours ago
0x095ea7b3
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0xa8b312c331e3eDaDc91Be427e3a9c06Cf135736B
0 ETH
0x8f20cefdced23fc1570673eaced2c046e161f2b594d76f8e67b5353ba140439d
mined
255 days 21 hours ago
0xb6f9de95
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
05
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0x07293300B92b3DF15F1772f777aF1756fc73A03B
0.
05
WETH
0x07293300B92b3DF15F1772f777aF1756fc73A03B
0x0000000000000000000000000000000000000000
1
403
192
015
.
299
178
124
870
800
404
BURN
0x07293300B92b3DF15F1772f777aF1756fc73A03B
0xa8b312c331e3eDaDc91Be427e3a9c06Cf135736B
11
225
536
122
.
393
424
998
966
403
233
BURN
0x07293300B92b3DF15F1772f777aF1756fc73A03B
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
268
009
674
922
.
143
021
850
322
877
192
BURN
0xcd8938c6a2a14bcafcba9d8e86f037b0f37826a51bd6f7087a51f9a7f97a966c
mined
255 days 23 hours ago
Transfer
0x2Abc22eb9A09EbBE7b41737CCde147F586EfeB6A
0x46Be89Ff0Ead0612601dC1c59892f741360Ad3Ed
0.
098
8
ETH