Address

0x17886bfA74D67902b97fda308672C127B96b749B

0.000047444146932 ETH
1.28 NOK

Confirmed
Balance0.000047444146932 ETH1.28 NOK
Transactions596
Non-contract Transactions590
Internal Transactions0
Nonce577
ContractQuantityValueTransfers#
0xUniversal0 0xU-3
1% club0 1%-7
ALCOH0 ALCOH-1
ANOTHER PEPE0 AP-3
Arena Deathmatch0 ARENA-3
BANANACAT0 Бананакат-6
BURN ADDRESS0 BURN-5
BUSINESS0 BUSINESS-5
Baby Calcium0 $BCal-3
Baby Calcium0 BCAL-3
BangBangSkeetSkeet0 BORAT-3
BeBe0 малыш-3
Bibi0 BIBI-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*).344415.458900571069074659 GENESIS-1
Bitcom0 BITCOM-6
Bitgold0 BTG-2
Blyat0 блять-2
Bone0 BONE-2
Boolish0 BOOLISH-3
Boomer0 BOOMER-2
Brainlet0 BRAINLET-8
CARLOS SAINZ0 SAINZ-2
CATECOIN0 CAT-13
COPIUM0 COPE-3
Calcium0 CAL-19
Calcium Killer0 SODA-2
CalciumPepe0 CALPEP-7
Cavachon0 CAVA-7
DADDY FINE0 DADDYFINE-3
DANGER0 DANGER-3
DEADMIGOS0 DEADMIGOS-3
Daddy Banana0 $DDBN-6
Dick Butt0 DICKBUTT-3
Dodo is Fine0 DINE-6
Doge Prophecy0 KEK-3
EGG0 EGG-9
Elon Cat15373075.092087632282664623 Schrödinger-1
FIRE0 FIRE-2
Fine Inu0 FINI-3
Frengate0 FGATE-3
Frogo0 FROGO-2
Fuck Banana0 FKBANANA-3
Gemini Ai0 GAI-6
Gumball Watterson0 GW-3
Hedz Tales0 HEDZ-4
Helium0 HE-3
Hobbes0 HOBBES-10
Honey0 мед-3
Hopium0 HOPE-13
Iron man0 IMAN-2
Just Read The Instructions0 JRTI-3
KIRBY0 KIRBY-9
LAKEE0 LAKEE-1
Lolcat0 LOLCAT-3
Loopy0 LOOPY-4
MKUltra0 MK-6
MORI0 MORI-4
Magnesium0 MAGNESIUM-1
Mr Pepe0 PEPE-2
MumuPepe0 MUPE-3
Of Course I Still Love You0 OCISLY-13
Of course i still love DOGE0 OCISLDOGE-3
Okay Fine0 OKay-6
Oxygen0 OXY-2
PEPE0 PEPE-3
Penguin Edition0 Odyssey-2
Pepe0 PEPE-3
Pepe0 Pepe-2
Pepe Doge0 PEGE-3
Pepe Prophecy0 KEK-2
PepeCripsOGTupacIceCube10🔵Inu1525588.993109281549444534 PEPECRIPS-1
Potassium0 POT-3
Real Banana Bird0 очиститься-2
Real Smurf Cat0 шайлушай-10
Reshib Inu0 RESHIB-4
Ryoshi0 SHIB-2
SAME COIN0 SAME-2
Schrodinger0 Dinger-9
Shiba0 SHIBA-2
Shiba Inu0 SHIB-2
Shiba Inu0 SHIB-4
Shiba Inu Classic0 SHIBC-8
Success Kid0 SKID-2
The Bear0 BEAR-11
The Real Calcium0 CAL-3
Trick0 TRICK-8
UPTOBER0 UP-3
UwU3862679.432926049533198879 UwU-1
WAFFLE0 WAFFLE-1
WHITE RICE7887969.383427368872249536 米饭-4
Waddle Dee0 WADDLE-2
Wanna know something hilarious? They have no idea what to do with you autistic fucks. Literal masters degee holding feds have debates, PowerPoints, talks, de-escalation training, and containment of negative thought exercises to de-radicalize agents that lurk here and elsewhere. I've been to the briefs. It's actually the reason I quit. They're so unbelievably incompetent and retarded that actionable counter-meme plans were drawn up and wargamed. I shit you not, middle aged men were thinking of ways to make Pepe the frog gay so nazis wouldn't want to use it anymore. They have nothing. Outside of blatant censorship, they have lost. They can't do anything about you all. The only semi smart thing they did was start accusing everyone of being a fed so they could trip up online movements from turning into actual demonstrations. That's it. That's all they've come up with in years of lurking.To recap , they can't meme ,they hire tranny therapists to help their poor radicalized lurking shitposters , they wanted to turn Pepe gay , they literally have no idea how to stop you autismos from memeing them into defeat,It's hilarious. Remember, every shitpost that makes them look like idiots actually infuriates them. Never stop0 FEDS-3
XXCOIN0 XX-3
YOYO0 YOYO-1
Z0 Z-9
gm6726687189.632300432715237029 GM-1
harrypotterobamasmurfcat911inu0 биткойн-2
nothing0 thing-7
passkeys.io0 PASSKEYS-3
ƎԀƎԀ0 ƎԀƎԀ-9
ʞ∀ſOM0 ʞ∀ſOM-2
カエルのペペ0 ペペ-2
环球股0.001 HQG-1
🍒 ⋆ 🍎 🎀 𝒮𝓃♡𝓊𝓉𝓃🍩𝓈𝑒 𝒫𝒶𝓇𝓉𝓎𝓈𝓁𝓊𝓉 🎀 🍎 ⋆ 🍒0 PARTYS-3
🍒 ⋆ 🍎 🎀 𝒮𝓃♡𝓊𝓉𝓃🍩𝓈𝑒 𝒫𝒶𝓇𝓉𝓎𝓈𝓁𝓊𝓉 🎀 🍎 ⋆ 🍒0 Partyslut-11

Transactions

ERC20 Token Transfers
 
0x17886bfA74D67902b97fda308672C127B96b749B
2532616566.16561251 WAFFLE-
ERC20 Token Transfers
 
0x17886bfA74D67902b97fda308672C127B96b749B
2432616566.16561251 ALCOH-
ERC20 Token Transfers
 
0x17886bfA74D67902b97fda308672C127B96b749B
1932616566.16561251 YOYO-
ERC20 Token Transfers
 
0x17886bfA74D67902b97fda308672C127B96b749B
2293270000 LAKEE-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0.333326108737848424 ETH5909.49 NOK9009.14 NOK
0x17886bfA74D67902b97fda308672C127B96b749B
 
0 ETH0.00 NOK0.00 NOK
ERC20 Token Transfers
0x17886bfA74D67902b97fda308672C127B96b749B
 
569783109833.292408720094493099 FROGO-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0 ETH0.00 NOK0.00 NOK
0x17886bfA74D67902b97fda308672C127B96b749B
 
0.1 ETH1772.89 NOK2702.80 NOK
ERC20 Token Transfers
 
0x17886bfA74D67902b97fda308672C127B96b749B
569783109833.292408720094493099 FROGO-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0 ETH0.00 NOK0.00 NOK
ERC20 Token Transfers
0x17886bfA74D67902b97fda308672C127B96b749B
 
6179.848531646154891401 PEPE-
0x17886bfA74D67902b97fda308672C127B96b749B
 
611805.004632969334248776 PEPE-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0 ETH0.00 NOK0.00 NOK
0x17886bfA74D67902b97fda308672C127B96b749B
 
0.1 ETH1772.89 NOK2702.80 NOK
ERC20 Token Transfers
 
0x17886bfA74D67902b97fda308672C127B96b749B
617984.853164615489140177 PEPE-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0 ETH0.00 NOK0.00 NOK
ERC20 Token Transfers
0x17886bfA74D67902b97fda308672C127B96b749B
 
85.048040915 BITCOM-
0x17886bfA74D67902b97fda308672C127B96b749B
 
8419.756050621 BITCOM-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0.15 ETH2659.33 NOK4054.20 NOK
ERC20 Token Transfers
 
0x17886bfA74D67902b97fda308672C127B96b749B
8504.804091536 BITCOM-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0 ETH0.00 NOK0.00 NOK
ERC20 Token Transfers
0x17886bfA74D67902b97fda308672C127B96b749B
 
15987623.480207764848924269 шайлушай-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0.272703538170477522 ETH4834.72 NOK7370.63 NOK
ERC20 Token Transfers
 
0x17886bfA74D67902b97fda308672C127B96b749B
15987623.480207764848924269 шайлушай-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0 ETH0.00 NOK0.00 NOK
ERC20 Token Transfers
0x17886bfA74D67902b97fda308672C127B96b749B
 
1071.944116006 UP-
0x17886bfA74D67902b97fda308672C127B96b749B
 
106122.467484651 UP-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0 ETH0.00 NOK0.00 NOK
0x17886bfA74D67902b97fda308672C127B96b749B
 
0.1 ETH1772.89 NOK2702.80 NOK
ERC20 Token Transfers
 
0x17886bfA74D67902b97fda308672C127B96b749B
107194.411600657 UP-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0 ETH0.00 NOK0.00 NOK
ERC20 Token Transfers
0x17886bfA74D67902b97fda308672C127B96b749B
 
65.864560521 BITCOM-
0x17886bfA74D67902b97fda308672C127B96b749B
 
6520.591491633 BITCOM-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0 ETH0.00 NOK0.00 NOK
0x17886bfA74D67902b97fda308672C127B96b749B
 
0.1 ETH1772.89 NOK2702.80 NOK
ERC20 Token Transfers
 
0x17886bfA74D67902b97fda308672C127B96b749B
6586.456052154 BITCOM-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0 ETH0.00 NOK0.00 NOK
ERC20 Token Transfers
0x17886bfA74D67902b97fda308672C127B96b749B
 
428573159248.390679547810557936 SHIBA-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0 ETH0.00 NOK0.00 NOK
0x17886bfA74D67902b97fda308672C127B96b749B
 
0.195464599671935401 ETH3465.36 NOK5283.02 NOK
ERC20 Token Transfers
 
0x17886bfA74D67902b97fda308672C127B96b749B
428573159248.390679547810557936 SHIBA-
0x17886bfA74D67902b97fda308672C127B96b749B
 
0 ETH0.00 NOK0.00 NOK
ERC20 Token Transfers
0x17886bfA74D67902b97fda308672C127B96b749B
 
10345947.775253210057616044 CAT-
0x17886bfA74D67902b97fda308672C127B96b749B
 
506951440.987407292823186187 CAT-