Address

0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3

0.000067608138742707 ETH
6.88 PHP

Confirmed
Balance0.000067608138742707 ETH6.88 PHP
Transactions139
Non-contract Transactions98
Internal Transactions0
Nonce83
ContractQuantityValueTransfers#
# ethapy.org1.4 Visit https://ethapy.org to claim rewards-1
# usd2023.com3999.99 Visit https://usd2023.com to claim rewards-1
$ bitbonus.tech70 Bonus. Visit https://bitbonus.tech to claim reward.-1
$ mPEPE.org0 Reward Token from https://mPEPE.org-1
0xSwapo.com12887771 0xSwapo.com-1
BigMouthFrog722.440113733591613956 BGBG-1
Convertible JPY Token0 CJPY-9
CorgiAI0 CORGIAI-2
EthFork2.com350 EthFork2.com-1
EТH..0 EТH-1
Happy Birthday Elon1000000 52-1
MAGA0 TRUMP-3
Pepe0 PEPE-6
SpongeBob0 SPONGE-3
USD Coin0 USDC-55
USD Coin0 USDC-1
USDC0 USDC-1
VoteFork.com800 VOTEFORK.COM-1
Wojak Coin0 WOJAK-5
dYdX0 DYDX-4
ЕТН...0 ЕТH-1
ContractTokensTransfers#
# yieldeth.net1 Visit yieldeth.net to claim rewards of ID 11
Reward Club [ayo8vfDI]1 Reward Club [wtFZhMwO] of ID 01
Unisocks NFT1 Unisocks of ID 21
apyether.org1 Airdrop of ID 01
genesis-eth.org1 claim rewards on genesis-eth.org of ID 01

Transactions

mined 34 days 21 hours ago
Airdrop (0xece8c31c)
ERC1155 Token Transfers
 
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
1 claim rewards on genesis-eth.org of ID 0
 
1 claim rewards on genesis-eth.org of ID 0
 
1 claim rewards on genesis-eth.org of ID 0
 
1 claim rewards on genesis-eth.org of ID 0
 
1 claim rewards on genesis-eth.org of ID 0
 
1 claim rewards on genesis-eth.org of ID 0
 
1 claim rewards on genesis-eth.org of ID 0
 
1 claim rewards on genesis-eth.org of ID 0
 
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*).
1 claim rewards on genesis-eth.org of ID 0
ERC20 Token Transfers
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0.0198 EТH-
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0.0198 ETH2548.46 PHP2015.11 PHP
mined 313 days 13 hours ago
Transfer (0xa9059cbb)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0 ETH0.00 PHP0.00 PHP
ERC20 Token Transfers
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
588.888469 USDC0.321875 ETH32758.15 PHP
mined 313 days 13 hours ago
Swap (0x5f575529)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0.154 ETH30417.31 PHP15673.04 PHP
ERC20 Token Transfers
 
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
513.862174 USDC0.280867 ETH28584.66 PHP
mined 313 days 13 hours ago
Swap (0x5f575529)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0 ETH0.00 PHP0.00 PHP
ERC20 Token Transfers
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
66183.768568040789664308 CORGIAI0.005302 ETH539.63 PHP
 
66183.768568040789664308 CORGIAI0.005302 ETH539.63 PHP
 
0.022490931370549055 WETH0.022497 ETH2289.55 PHP
 
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
75.026295 USDC0.041008 ETH4173.49 PHP
mined 313 days 13 hours ago
Approve (0x095ea7b3)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0 ETH0.00 PHP0.00 PHP
mined 333 days 21 hours ago
Transfer (0xa9059cbb)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0 ETH0.00 PHP
ERC20 Token Transfers
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
5585.787207 USDC3.053080 ETH310721.07 PHP
mined 333 days 21 hours ago
Execute (0x3593564c)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0 ETH0.00 PHP
ERC20 Token Transfers
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
4.112599823 TRUMP-
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
407.147382565 TRUMP-
 
1.490467386222772328 WETH1.490843 ETH151727.56 PHP
 
5599.786673 USDC3.060731 ETH311499.82 PHP
 
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
5585.787207 USDC3.053080 ETH310721.07 PHP
mined 333 days 21 hours ago
Approve (0x095ea7b3)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0 ETH0.00 PHP
mined 333 days 21 hours ago
Transfer (0xa9059cbb)
ERC20 Token Transfers
 
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
411.259982388 TRUMP-
mined 351 days 9 hours ago
Deposit For Burn (0x6fd3504e)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0 ETH0.00 PHP0.00 PHP
ERC20 Token Transfers
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
3459.674069 USDC1.890989 ETH192451.59 PHP
mined 351 days 9 hours ago
Approve (0x095ea7b3)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0 ETH0.00 PHP0.00 PHP
mined 351 days 9 hours ago
Transfer (0xa9059cbb)
ERC20 Token Transfers
 
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
3459.674069 USDC1.890989 ETH192451.59 PHP
mined 354 days 6 hours ago
Deposit For Burn (0x6fd3504e)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0 ETH0.00 PHP
ERC20 Token Transfers
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
13590.623388 USDC7.428363 ETH756006.79 PHP
mined 354 days 6 hours ago
Approve (0x095ea7b3)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0 ETH0.00 PHP
mined 354 days 6 hours ago
Transfer (0xa9059cbb)
ERC20 Token Transfers
 
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
13590.623388 USDC7.428363 ETH756006.79 PHP
 
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
0 ETH0.00 PHP0.00 PHP
mined 359 days 8 hours ago
Transfer (0xe19c2253)
ERC20 Token Transfers
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
3.5 ЕТH-
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
3.5 ETH609621.91 PHP356205.50 PHP
 
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
2.9654301 ETH516511.76 PHP301800.72 PHP
 
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
0.39136599 ETH68167.22 PHP39830.49 PHP
mined 362 days 15 hours ago
Transfer (0xa9059cbb)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0 ETH0.00 PHP0.00 PHP
ERC20 Token Transfers
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
2340.541678 USDC1.279293 ETH130197.52 PHP
mined 362 days 15 hours ago
Exchange (0x5c9c18e2)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0 ETH0.00 PHP0.00 PHP
ERC20 Token Transfers
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
395603.145742973252499306 CJPY1.269886 ETH129240.12 PHP
 
395603.145742973252499306 CJPY1.269886 ETH129240.12 PHP
 
2343.117797895370990627 crvUSD1.281521 ETH130424.28 PHP
 
2343.117797895370990627 crvUSD1.281521 ETH130424.28 PHP
 
2341.178558 PYUSD1.279431 ETH130211.50 PHP
 
2341.178559 PYUSD1.279431 ETH130211.50 PHP
 
2340.541678 USDC1.279293 ETH130197.52 PHP
 
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
2340.541678 USDC1.279293 ETH130197.52 PHP
mined 362 days 15 hours ago
Approve (0x095ea7b3)
0x2f234B7c3762327cDbE85FCaB3b87e880e13e3f3
 
0 ETH0.00 PHP0.00 PHP