Address

0x7B89513c3Aa412D627fBeA19706fc0aa8745588e

0.000162337964061 ETH

Confirmed
Balance0.000162337964061 ETH
Transactions545
Non-contract Transactions545
Internal Transactions0
Nonce530
ContractQuantityValueTransfers#
0XBUILDER TOOLS101029.716580743 0XERC1
0x Leverage0 0XL3
20490 20495
ANON BOT725.401998919041242392 $ANON1
Azrael0 AZRAEL3
BOBO561200.021636109 BOBO1
BONKLER0.67333048 BONKLER1
BTC THE FINE0 BTCFINE6
Baby Sally139168581580.467402182 BSALLY1
Beast0 BEAST3
Beeple vs 𝓜𝓪𝓽𝓽 𝓕𝓾𝓻𝓲𝓮0 BEEMATT3
Bent Protocol2218066.387397537 BENT1
Bibi981247.564629518 BIBI1
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*).327012.688874517043936695 GENESIS1
BitcoinEthereumTetherBNBXRPUSDCDogecoinCardanoSolanaTronMaticLitecoinPolkadotShibaInuDaiBitcoinCashWrappedBitcoinAvaxTonLinkStellarLEOUNITUSDAtomMoneroOKBEthereumClassicHederaInternetComputerFilecoinMantleLidoDaoAptosArbitrumCronosVechainNEARQuantOptismMakerTheGraphAaveXDCNetworkAlgorandTheSandboxAxieInfinityMultuversXStacksTezosUSDDThetaNetworkBitcoinSVManaSynthetixInjectiveApeCoinFantomNeiRendereCashFlowKavaChilizKucoinTokenGalaCurveDaoTOkenPaxDollarRocketPoolKlaytnZcashPaxGoldIOTATetherGoldFraxShareTerraClassicCasperGMXPepe0 CRYPTO3
Bob0 BOB6
Boba0 BOBA2
Brother of Pepe372846361.149893525 FORG1
Bulls AI4330991.862690304436847684 BULLSAI1
Crazy Milady0 MILADY3
Cyber Pepe0 CEPE3
DINO PEPE0 $DPEPE3
Degen.market0 DEGEN2
Dick Butt0 DICKBUTT8
DolanCoin64258465.522169168984221278 Dolan1
Drunkard0 D R U N K A R D6
Dumb Hippo273305801.108377268 HAROLD1
FEFE0 $FINEKILLER3
FINE 2.00 FINE23
FKPEPE0 FKPEPE3
FLOKI221523.37719351095651718 FlOKI1
FOXY0 FOXY2
FTXBOT13634.28858964 FTXBOT1
Fatt Murie2707476606.804458728 FATT1
Fine 2.00 FINE22
Fine Inu1413877544873.709462099 FINE INU1
Fine Pepe0 FEPE10
Fine is me0 FIM3
FineFrog0 FINEFROG3
Fite Me !0 FITE3
FriendDAO0 FDAO3
GOBLINZ0 ᘜOᗸᒪINZ6
GORLAX108575.102636762 GORLAX1
GRUBBIE110268.17342589 GRUBBIE1
Generational Wealth Generator0 GWG3
Golden One2995252.754172273435653325 𝙶𝟙1
HEDZ0 HEDZ9
HEIMAO0 HEIMAO2
HarryPotterObamMattFurie1Meme2348362.921225154 PEPE1
HarryPotterObamaMegaman10Inu156886.815740164 ETHEREUM1
Homeless Hamster0 Хэмптер3
IPHONE 15 COMMUNITY0 IPHONE 153
Indestructible Nokia 33100 NOKIA3
InterChain Staking Derivatives3353200.029608405 ICSD1
It's OK3737555.423989384899993468 OK1
Killer Pickle166908.369381043 KPICKLE1
Kitty Puppy2226.094059163 CATDOG2
Kroog Coin0 KROOG2
LEEKSPIN0 LEEK6
LUCKY DRAGON0 LUCKYMF3
Lambo0 LAMBO2
Loong0 LOONG2
Lord Inu0 LINU3
Love0 LOVE2
LowIQ1047.642882992920225908 LOWIQ2
Luminus0 Luminus2
MERCY0 MERCY2
MISHA0 MISHA3
MLG2626492.47364212 MLG1
MPEPE24648.926065075 MPEPE1
MULTI DEX Aggregator0 MULTI4
Magic Autism Bux0 BUX2
MarioKartRacingO'DoyleRulesBananaBlowGuns#Wrecked0 PEELY3
Matt furie's ARTS0 $ARTS3
Maui Wowwee0 MAUIWOWWEE5
Meff2245510.84546896636045043 MEFF1
Meme Capital0 MC3
Mercy Coin1028567.376605035 MERCY1
Mrs This is Fine!3282.5733475 MrsFine1
No Cap0 NCAP3
OKAY546312033.207363694894249904 OKAY1
P E P E0 P E P E3
PEPE0 PEPE3
PEPE CLASSIC0 PEPEC3
PEPE FINE0 PEPEF3
PEPE II125723719407.467605762 PEPE1
PEPE KART RACE2541657.975546969 PEPE KART RACE1
PEPE ZEUS214927.644938091 PEZE1
PEPECOIN319404.032084564 PEPECOIN1
PEPEMUU0 PEPEMUU3
PEPEP23153661452.821952788667514563 PEPEP1
PEPEwasFINE0 PEPEFINE3
PIBA0 PIBA8
PICKLE RICK108879.295225477 RICK3
POPO6874737.062494653 POPO1
PROPHET_Dividends0 PROPHET_Dividends2
Pepe Banana260918.720043229 PANA1
Pepe Classic5814930.40090222 PEPEC1
Pepe Wars912138.51333629 PEPEX1
Pinkpartyfrog Yellowhood0 $PIPAFROYE3
Pita568550.557218979114771472 PITA1
Plyde443706.636195187 PLYDE1
Poge0 POGE4
Pontifex0 PONTIFEX2
Prophet0 PROPHET3
Question Hound0 HOUND3
RANSOM0 RANSOM3
RED HOT COCK0 RHC11
REKT979530670796.297810285 REKT1
RHC Predator4628572.262742026414400558 HAWK1
Real Apple Cat1945169.53691445 яблочныйкот1
Real Banana Dog29885725.23552056 банановая1
Real Pineapple Owl0 дегенерация2
Real Pineapple Owl0 Pineowl2
Real Smurf Inu234545.880717141 СмурфИну1
Reprint196796.924509008 REPRINT1
Revso APP0 RevSo3
Roronoa Zoro0 ZORO5
SAME COIN410460.13274442734201705 SAME1
SHIFU0 SHIFU3
SMURFPEPE722162181312.780534835 SPEPE1
SPARTA0 SPARTA3
Shen Long2500884257.358085688 SHENLONG1
Shut Up and Take my Money0 $SHUTUP3
Smurf Cat220855690.181400176 SCAT1
Smurfs214381.139803379 SMURF1
SocialFi0 SOCIAL4
SonicVsTailsVsKnuckles95721.378192489 RINGS1
Success Kid0 SKID2
THIS IS NOT FINE0 NOTFINE2
TOG0 TOG2
TRIPPER PEPE87109.79730996 TRIPPE1
Techno Mechanicus0 Tau11
Televisa0 TESA4
This is Good160470.651536963 GOOD4
This is Not Fine505437.45180951 NotFine1
Together132647401.154170786 TGH1
Tripper Pepe0 TRIPPER6
Viral184291.423241764 VIRAL1
Vivek0 GCR2
WAPPLE2292820.700439772 WAPPLE1
WAT0 WAT10
WELL180986.269234740699384702 WELL1
Wapple3514193.050153328 WAPPLE1
We live We love We lie47787034.653910194122485388 WLWLWL1
Yoba Coin0 YOBA5
ZlurpeeZoofusAndymanBobcatBirdDogGrubbieShaggonomicsSocketTheMummyGoobReptangelloGhostskullTheKidKlickerSoselyGorthSpuciHorribleBreathDickChainyPockfaceSnaptornRedHotCockGreenDeathGritShitterBigWulfGhostDeathCreepKroogWitchBeastShadowDJCockChomperProbisGlobDrainDealerZillionaraPinchwickCocktopBeastHuffyReptilianShrekLickerForgGraundiRinesyZegladoid3ZXReplicatorSirGagaLookerAntiolGasspasValkoreQuackshitGumboTreesaBliffPlydeBrainyTongueRainbowMormecBlubbleGayDragonGurumonCandyEyezDoinkerZappaForallRainbowKragDoldrumandIckChumGrinderDolphinPepethePenguinSealixTursulaKaronGremlinGorlaxDogfaceHe-DevilTrollionBigWaveLiposuckerFatFuckFlubbaPissportSnortMoonCreamyPorkySodaGlaxZoinkCatMcGooLandwolfSmogBoochiePiperSnarlaDuckyDuckWhaleDoggyDoggDorkLord151988360.490853958 ZOGZ1
Zoolie3964293487.145402968 ZOOLIE1
backrooms85705.11977818434399138 BACK1
kek435.765174839983673794 KEK2
wen0 WEN3
ƎԀƎԀ0 ƎԀƎԀ3
ǝᴉqqnɹפsᴉqoɹԀsǝlqqnlqƃɐɹʞʍoquᴉɐɹuoᴉlloɹ┴ɥɔʇᴉMxɐlɹoפʎɯɐǝɹƆuooWsnɟooZɥʇɐǝpuǝǝɹפʎuᴉɐɹqllɐɹoℲɹǝʞɔnsodᴉ˥ǝpʎlԀɥʇɹoפɔǝɯɹoWʍopɐɥSʇsɐǝqʎuᴉɐɥƆʞɔᴉpǝnƃuo┴ƃuo˥doʇʞɔoƆʞɔIpu∀ɯnɹplopʇɐɔʞuᴉoZƃoɯSlᴉʌǝp-ǝHǝɔɐɟƃopxᴉlɐǝSuoɹɐʞɐpoSʎʞɹoԀʇǝʞɔoSʞɔᴉʍɥɔuᴉԀʍoquᴉɐɹloᴉʇu∀ɟlnMƃᴉqᴉpunɐɹפɹǝʇʇᴉɥSʇᴉɹפɥʇɐǝɹqǝlqᴉɹɹoHɹǝʞɔᴉlʞƃooɹʞuɐᴉlᴉʇdǝɹɹǝʞɔᴉ˥ʞǝɹɥSʎlǝsoSʎɯɯnWǝɥ┴ɐddɐZXZƐpᴉopɐlƃǝZɐɹɐuoᴉllᴉZʇɐɔqoqɹǝdɯoɥƆʞɔoƆɹǝʞuᴉopuᴉɐɹpqolפqooפuoɯnɹnפʎɟɟnHʞɔoƆʇoHpǝɹɹoʇɐɔᴉldǝɹʎsǝuᴉɹuɹoʇdɐuSɐsǝǝɹ┴xɐlפoqɯnפʞɔnpʎʞɔnpɹǝpuᴉɹפɯnɥƆʇᴉɥsʞɔɐnQsɔᴉɯouoƃƃɐɥSuᴉɥdlopollǝƃuɐʇdǝɹʇsɐǝqǝɔɐɟʞɔoԀɹǝdᴉԀʇɹodssᴉԀɐlɹɐuSᴉɔndSƃoppɹᴉqɐƃɐפɹᴉSɐqqnlℲʇsoɥפdǝǝɹƆɥʇɐǝpuoƃɐɹpʎɐפuᴉnƃuǝԀɹǝlɐǝpɐlnsɹn┴ɟɟᴉlqƃƃopʎƃƃopʞɔnℲʇɐℲsɐdssɐפllnʞsʇsoɥפuᴉlɯǝɹפɹǝʞoo˥ooפɔWʇɹouSɹǝddᴉlℲzǝʎǝʎpuɐƆƃɹoℲǝᴉɥɔooqǝlɐɥMǝɹoʞlɐΛpᴉʞǝɥ┴ǝʌɐMƃᴉquɐɯʎpu∀ǝǝdɹnlZſpɹǝpɐΛʞɹopʞɹoqɟloMpuɐ˥ʎddoHpɹo˥ʞɹopǝdǝԀ184020681.257411 MATT1
ʂղąքէօɾղ0 SNAPTORN3
ᖇEᗪ ᕼOT ᑕOᑕK0 ᖇEᗪᕼᑕ2
ᗪOᖇK ᑕᗩT0 MEOW3
Ⲙⲟⲟⲛⲥⲁⲧⲥⲏⲉꞅ83610.844138126 MOONC1
ㄒ尺丨卩卩乇尺乙4878221.180389338 ㄒ尺丨卩卩乇尺乙2
NΞ♢ PΞPΣ0 NEPE3
𝓒𝓞𝓒𝓚 𝓒𝓗𝓞𝓜𝓟𝓔𝓡0 ZOGZ43
𝓟𝓔𝓟𝓔0 𝓟𝓔𝓟𝓔3
𝕏 - GirlFriend2709170.66152068 𝕏GFRIEND1
🐸Pepe Lord🐸0 PepeL3

Transactions

0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.007568317583140382 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.004425249848807802 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
0 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.04 ETH
ERC20 Token Transfers
 
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
618.670419367041269047 LOWIQ
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.05 ETH
ERC20 Token Transfers
 
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
428.972463625878956861 LOWIQ
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.02 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.03 ETH
ERC20 Token Transfers
 
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
23153661452.821952788667514563 PEPEP
 
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
0.164042 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.00140284548524286 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.007132148406260456 ETH
ERC20 Token Transfers
 
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
217.047606995133152219 KEK
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.015 ETH
ERC20 Token Transfers
 
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
218.717567844850521575 KEK
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.015 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0 ETH
ERC20 Token Transfers
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
2630.91497788 WEN
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
128914.8339166 WEN
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.01 ETH
ERC20 Token Transfers
 
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
47787034.653910194122485388 WLWLWL
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.02 ETH
ERC20 Token Transfers
 
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
2500884257.358085688 SHENLONG
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.02 ETH
ERC20 Token Transfers
 
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
131545.74889448 WEN
 
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
0.07982464 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.008657827638191293 ETH
ERC20 Token Transfers
 
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
561200.021636109 BOBO
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0 ETH
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
 
0.01 ETH
ERC20 Token Transfers
 
0x7B89513c3Aa412D627fBeA19706fc0aa8745588e
132647401.154170786 TGH