Address

0xA420872a164644469C6a5dA5C1B2740FD3f13667

0.122712889368746236 ETH
301.79 USD

Confirmed
Balance0.122712889368746236 ETH301.79 USD
Transactions1041
Non-contract Transactions989
Internal Transactions0
Nonce951
ContractQuantityValueTransfers#
! Chickencoin Rewards By chicken-dao.xyz129000 $CHKN Rewards By https://chicken-dao.xyz-1
! HOPPY Reward Token (Website: hoppyfrog.org)89700 Get $HOPPY reward at https://hoppyfrog.org-1
# BANANA Reward | bananameme.net7.8 BANANA Reward | Receive at https://bananameme.net-1
# StakeEther.net1.7 Visit StakeEther.net to claim rewards-1
# chickencoin.gift783158000 CHKN Airdrop Ticket | https://chickencoin.gift-1
# dcicloudai.net800 DCI Incentive Ticket | https://dcicloudai.net-1
# fofar.org1 FOFAR Reward Token (https://fofar.org)-1
$ ETH200k.com200000 $ Visit ETH200k.com to claim $200k-1
$ KEKEC Award Chip (https://kekec.app)850000 KEKEC Award Chip (https://kekec.app)-1
$ getETH.org1.4 Visit getETH.org to claim rewards-1
$1 CAR0 $1CAR-3
$SPIKE Coin0 $SPIKE-2
0xOpen0 0xO-3
AITaxBot0 AITAX-3
ARCADE300000 ARCADE-1
ATOM AI589303.190813448 ATOM-1
Abattoir of Zir0.000009258 DIABLO-2
Akira Inu38819.796632149 AKINU-2
Akira Inu442178001.390862593115867066 AKIRA-1
Anita Max Wynn0 WYNN-2
Any.trade0 ATRADE-2
Apollo Inu455.316224647 APOLLO-3
ApuToken0 APU-2
Arsha Finance129.831781593 $ARSHA-2
Astaghfirullah0 Astaghfirullah-2
Astaghfirullah0 Astaghfirullah-2
Auditus Pad166.378228406859810301 AUDIT-1
Azure AI0 Azure AI-1
BABYTROLL0 BABYTROLL-3
BANANA Airdrop Ticket | banana-gun.app250000 # banana-gun.app-1
BENANCE0 BENANCE-2
BIDEN0 BIDEN-1
BLING ELON0 BLINGLON-2
BOBO0 BOBO-2
BRAI0 BRAI-1
BRCLauncher0 BRC-3
Baby pepeCoin0 BabypepeCoin-2
Banana6.96450302680879516 BANANA-3
Based Retard Gang0 𝕭𝕽𝕲-2
Bear Inu126115.329141788107680767 Bear-2
Biao Classic0.00087823786723581 BIAOC-3
BitRunes0 BRUNE-3
BitVenture AI0 BIVE-2
Bitcoin: A Peer-to-Peer Electronic Cash System Satoshi Nakamoto [email protected] www.bitcoin.org Abstract. A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution. Digital signatures provide part of the solution, but the main benefits are lost if a trusted third party is still required to prevent double-spending. We propose a solution to the double-spending problem using a peer-to-peer network. The network timestamps transactions by hashing them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work. The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power. As long as a majority of CPU power is controlled by nodes that are not cooperating to attack the network, they'll generate the longest chain and outpace attackers. The network itself requires minimal structure. Messages are broadcast on a best effort basis, and nodes can leave and rejoin the network at will, accepting the longest proof-of-work chain as proof of what happened while they were gone. 1. Introduction Commerce on the Internet has come to rely almost exclusively on financial institutions serving as trusted third parties to process electronic payments. While the system works well enough for most transactions, it still suffers from the inherent weaknesses of the trust based model Completely non-reversible transactions are not really possible, since financial institutions cannot avoid mediating disputes. The cost of mediation increases transaction costs, limiting the minimum practical transaction size and cutting off the possibility for small casual transactions, and there is a broader cost in the loss of ability to make non-reversible payments for nonreversible services. With the possibility of reversal, the need for trust spreads. Merchants must be wary of their customers, hassling them for more information than they would otherwise need. A certain percentage of fraud is accepted as unavoidable. These costs and payment uncertainties can be avoided in person by using physical currency, but no mechanism exists to make payment over a communications channel without a trusted party What is needed is an electronic payment system based on cryptographic proof instead of trust, allowing any two willing parties to transact directly with each other without the need for a trusted, allowing any two willing parties to transact directly with each other without the need for a trusted third party. Transactions that are computationally impractical to reverse would protect sellers from fraud, and routine escrow mechanisms could easily be implemented to protect buyers. In this paper, we propose a solution to the double-spending problem using a peer-to-peer distributed timestamp server to generate computational proof of the chronological order of transactions. The system is secure as long as honest nodes collectively control more CPU power than any cooperating group of attacker nodes. 2. Transactions We define an electronic coin as a chain of digital signatures. Each owner transfers the coin to the next by digitally signing a hash of the previous transaction and the public key of the next owner and adding these to the end of the coin. A payee can verify the signatures to verify the chain of ownership. The problem of course is the payee can't verify that one of the owners did not double-spend the coin. A common solution is to introduce a trusted central authority, or mint, that checks every transaction for double spending. After each transaction, the coin must be returned to the mint to issue a new coin, and only coins issued directly from the mint are trusted not to be double-spent. The problem with this solution is that the fate of the entire money system depends on the company running the mint, with every transaction having to go through them, just like a bank We need a way for the payee to know that the previous owners did not sign any earlier transactions. For our purposes, the earliest transaction is the one that counts, so we don't care about later attempts to double-spend. The only way to confirm the absence of a transaction is to be aware of all transactions. In the mint based model, the mint was aware of all transactions and decided which arrived first. To accomplish this without a trusted party, transactions must be publicly announced [1], and we need a system for participants to agree on a single history of the order in which they were received. The payee needs proof that at the time of each transaction, the majority of nodes agreed it was the first received. 3. Timestamp Server The solution we propose begins with a timestamp server. A timestamp server works by taking a hash of a block of items to be timestamped and widely publishing the hash, such as in a newspaper or Usenet post [2-5]. The timestamp proves that the data must have existed at the time, obviously, in order to get into the hash. Each timestamp includes the previous timestamp in its hash, forming a chain, with each additional timestamp reinforcing the ones before it 4. Proof-of-Work To implement a distributed timestamp server on a peer-to-peer basis, we will need to use a proof of-work system similar to Adam Back's Hashcash [6], rather than newspaper or Usenet posts. The proof-of-work involves scanning for a value that when hashed, such as with SHA-256, the hash begins with a number of zero bits. The average work required is exponential in the number of zero bits required and can be verified by executing a single hash. For our timestamp network, we implement the proof-of-work by incrementing a nonce in the block until a value is found that gives the block's hash the required zero bits. Once the CPU effort has been expended to make it satisfy the proof-of-work, the block cannot be changed without redoing the work. As later blocks are chained after it, the work to change the block would include redoing all the blocks after it. The proof-of-work also solves the problem of determining representation in majority decision making. If the majority were based on one-IP-address-one-vote, it could be subverted by anyone able to allocate many IPs. Proof-of-work is essentially one-CPU-one-vote. The majority decision is represented by the longest chain, which has the greatest proof-of-work effort invested in it. If a majority of CPU power is controlled by honest nodes, the honest chain will grow the fastest and outpace any competing chains. To modify a past block, an attacker would have to redo the proof-of-work of the block and all blocks after it and then catch up with and surpass the work of the honest nodes. We will show later that the probability of a slower attacker catching up diminishes exponentially as subsequent blocks are added. To compensate for increasing hardware speed and varying interest in running nodes over time the proof-of-work difficulty is determined by a moving average targeting an average number of blocks per hour. If they're generated too fast, the difficulty increases. 5. Network The steps to run the network are as follows: 1) New transactions are broadcast to all nodes 2) Each node collects new transactions into a block. 3) Each node works on finding a difficult proof-of-work for its block 4) When a node finds a proof-of-work, it broadcasts the block to all nodes. 5) Nodes accept the block only if all transactions in it are valid and not already spent 6) Nodes express their acceptance of the block by working on creating the next block in the chain, using the hash of the accepted block as the previous hash. Nodes always consider the longest chain to be the correct one and will keep working on extending it. If two nodes broadcast different versions of the next block simultaneously, some nodes may receive one or the other first. In that case, they work on the first one they received, but save the other branch in case it becomes longer. The tie will be broken when the next proof of-work is found and one branch becomes longer; the nodes that were working on the other branch will then switch to the longer one. New transaction broadcasts do not necessarily need to reach all nodes. As long as they reach many nodes, they will get into a block before long. Block broadcasts are also tolerant of dropped messages. If a node does not receive a block, it will request it when it receives the next block and realizes it missed one. 6. Incentive By convention, the first transaction in a block is a special transaction that starts a new coin owned by the creator of the block. This adds an incentive for nodes to support the network, and provides a way to initially distribute coins into circulation, since there is no central authority to issue them a way to initially distribute coins into circulation, since there is no central authority to issue them. The steady addition of a constant of amount of new coins is analogous to gold miners expending resources to add gold to circulation. In our case, it is CPU time and electricity that is expended. The incentive can also be funded with transaction fees. If the output value of a transaction is less than its input value, the difference is a transaction fee that is added to the incentive value of the block containing the transaction. Once a predetermined number of coins have entered circulation, the incentive can transition entirely to transaction fees and be completely inflation free. The incentive may help encourage nodes to stay honest. If a greedy attacker is able to assemble more CPU power than all the honest nodes, he would have to choose between using it to defraud people by stealing back his payments, or using it to generate new ins. He ought to find it more profitable to play by the rules, such rules that favour him with more new coins than everyone else combined, than to undermine the system and the validity of his own wealth. 7. Reclaiming Disk Space Once the latest transaction in a coin is buried under enough blocks, the spent transactions before it can be discarded to save disk space. To facilitate this without breaking the block's hash, transactions are hashed in a Merkle Tree [7][2][5], with only the root included in the block's hash. Old blocks can then be compacted by stubbing off branches of the tree. The interior hashes do not need to be stored. A block header with no transactions would be about 80 bytes. If we suppose blocks are generated every 10 minutes, 80 bytes * 6 * 24 * 365 = 4.2MB per year. With computer systems typically selling with 2GB of RAM as of 2008, and Moore's Law predicting current growth of 1.2GB per year, storage should not be a problem even if the block headers must be kept in memory. 8. Simplified Payment Verification It is possible to verify payments without running a full network node. A user only needs to keep a copy of the block headers of the longest proof-of-work chain, which he can get by querying network nodes until he's convinced he has the longest chain, and obtain the Merkle branch linking the transaction to the block it's timestamped in. He can't check the transaction for himself, but by linking it to a place in the chain, he can see that a network node has accepted it, and blocks added after it further confirm the network has accepted it. As such, the verification is reliable as long as honest nodes control the network, but is more vulnerable if the network is overpowered by an attacker. While network nodes can verify transactions for themselves, the simplified method can be fooled by an attacker's fabricated transactions for as long as the attacker can continue to overpower the network. One strategy to protect against this would be to accept alerts from network nodes when they detect an invalid block, prompting the user's software to download the full block and alerted transactions to confirm the inconsistency. Businesses that receive frequent payments will probably still want to run their own nodes for more independent security and quicker verification 9. Combining and Splitting Value Although it would be possible to handle coins individually, it would be unwieldy to make a separate transaction for every cent in a transfer. To allow value to be split and combined, transactions contain multiple inputs and outputs. Normally there will be either a single input from a larger previous transaction or multiple inputs combining smaller amounts, and at most two outputs: one for the payment, and one returning the change, if any, back to the sender. It should be noted that fan-out, where a transaction depends on several transactions, and those transactions depend on many more, is not a problem here. There is never the need to extract a complete standalone copy of a transaction's history. 10. Privacy The traditional banking model achieves a level of privacy by limiting access to information to the parties involved and the trusted third party. The necessity to announce all transactions publicly precludes this method, but privacy can still be maintained by breaking the flow of information in another place: by keeping public keys anonymous. The public can see that someone is sending an amount to someone else, but without information linking the transaction to anyone. This is similar to the level of information released by stock exchanges, where the time and size of individual trades, the tape, is made public, but without telling who the parties were. As an additional firewall, a new key pair should be used for each transaction to keep them from being linked to a common owner. Some linking is still unavoidable with multi-input transactions, which necessarily reveal that their inputs were owned by the same owner. The risk is that if the owner of a key is revealed, linking could reveal other transactions that belonged to the same owner. 11. Calculations We consider the scenario of an attacker trying to generate an alternate chain faster than the honest chain. Even if this is accomplished, it does not throw the system open to arbitrary changes, such as creating value out of thin air or taking money that never belonged to the not going to accept an invalid transaction as payment, and honest nodes will never accept a block attacker. Nodes are containing them. An attacker can only try to change one of his own transactions to take back money he recently spent. The race between the honest chain and an attacker chain can be characterized as a Binomial Random Walk.12366.949593200637096397 BITCOIN-1
BlackRock USD Institutional Digital Liquidity0 BUIDL-2
BreadCoin0 BRD-6
BrettLandwolfAndyPepe118723661.042529892 BLAP-1
Burts AI0 BURTS-2
CORONA0 CORONA-2
CYBER ELON204.281530329 CYBERELON-2
Catopia1760000000 Cats-1
CeDeFiAi0 CDFi-2
Changpeng Zhao0.000000002 CZ-2
Chickencoin0 CHKN-15
Chief Troll Officer0 CTO-2
ChinaFSD137975467113.989943605762103488 CHINAFSD-1
ChowDAO0 CHOW-3
Clarus the Dogcow0 DOGCOW-2
Clay0 CLAY-2
Cloudnet Ai0 CNAI-3
Codename: Kaiten0 KAI-4
CorpAI0 CAI-3
Cryptensor0 CRYPT-3
Cryptter2786927497.158741352601041891 Cryptter-1
Cz Inu143745.968892815 CZU-1
DECRYPT NETWORK0 DECRYPT-3
DEV SMASHED HIS KEYBOARD0 hixokdkekjcjdksicndnaiaihsbznnxnxnduje-2
Dark MAGA0 DMAGA-5
DarkMatter0 DMT-6
Decentralized Cloud Infrastructure0.000000000000000001 DCI-4
Deflation12364.789802804 DEFLATION-1
Degen Communism0 DCM-2
Degen Communism0 DC-2
Degen Communism0 DECOM-2
Diamond0 DIAMOND-2
Dinger Token0 DINGER-2
Dispersion0 DPS-2
DogTag0 DTAG-2
Dogepper0 DOGEPPER-2
Dogereum0 dETH-2
Domain Money2439.047991392 DOMAINMONEY-2
Donald The Trump0 DUCK-2
Dripe Coin0 DRIPE-3
Edison0 EDISON-2
FATHER0 FATHER-1
Fame AI0 FAME AI-1
Fanatico0 FCO-3
FlickFloat132361.778883372662845317 FLICK-2
Flokitama276000000000000000000 Flokitama-1
Flovi Inu0 FLOVI-3
Fofar0 FOFAR-6
FomoSwap0.092353480485931969 FOMOSWAP-1
Free CZ2074246.484073568 PRISON-1
Free Cz2400555.054896780332908987 FREECZ-1
FreeCZ200529.075866126 FREECZ-1
Froge0 FROGE-2
Fubuki Token10040.650912231263314741 FUBUKI-2
Fuse Token0 FUSE-2
Fusion Systems10862159.214460218 FUSION-1
GRIMJA111041340327246.803491681 GRIMJA-2
GRIMSHIB Token125994.888346493 GRIMSHIB-3
GameGPT by PRISM0 Gamegptofficial-1
GrimDoge277860.057545213 GD-2
Grimace Coin0 GRIM-5
Grimace Coin0 GRIMACE-3
Grimace Coin9219721.458351469 GRIM-1
Grok by Grōk.com0 Grōk-2
Halving0 HALVING-3
Hitensor AI0 HTAO-3
Holdenomics0 ʜᴏʟᴅᴇɴᴏᴍɪᴄꜱ-1
Hoppy The Frog0 HOPPY-2
HostileZoneOfficial0 Htz-6
HotHoneyBun382959338.95384949383188524 HHB-1
IVANKA TRUMP0 IVANKA-2
InFi0 8FI-3
InFi_DividendTracker0 InFi_DividendTracker-2
InsureX0 INSX-3
Ionic Pocket Token0 INP-6
James Bond0 BOND-2
Je Maple syrup0 Syrup-3
Jesus0 RAPTOR-2
JustAnEgg3954054053.07 EGG-1
KAIJUNO80.000000342679696132 KAIJU-5
Kabochan0 KABO-2
Kanpai0 KPAI-3
Kennedy240 RFKJR-2
KingShib180000000000 KingShib-1
KongFu0 KONGFU-2
KongTama4622063693.894880657 KongTama-1
Kuromi Special0 KUROMI-2
Lara Croft750000 CROFT-1
Let's Go Brandon0 LGB-9
LiquidLayer Token0 LILA-2
MANEKI-NEKO9395.523498003087917195 NEKO-2
MCREFI_DividendTracker0 MCREFI_DividendTracker-2
MEME KONG0 MKONG-4
MEVShare66251.490261667427054225 MEVS-1
MINESHIELD0 MNS-3
MLG0 MLG-2
MOONSHOT0 MOON-3
MTGA1104280674.037529399 MTGA-1
Magneto0 Magneto-3
Marvin Inu10745556.969369415 MARVIN-3
McDoge0 MCDOGE-6
McDogenalds DAO39925840218486.288458212 MDD-3
McKong0 McKong-2
McReFi0 MCREFI-3
McShib316316485236230531.454217125 McShib-2
McShiba0 McShib-3
Meatwad0 MEATWAD-3
Media Matters150000 MEDIA-1
Meishu715543.39555746 MEISHU-1
Mercury Inu348437.226112829 HAM-2
Merit Trading AI8710020.937650067996554924 MTAI-1
MetaPaco1.99465814292413234 MPAC-2
Mistral AI0 MisAI-1
Mojo0 MOJO-3
Monke coin0 MONKE-2
Monkette0 MONKETTE-2
Monster Truck0 MONSTER-2
Mump0 MUMP-2
NFL41357102.241492539 NFL-1
NVIDIA AI0 NVIDIA AI-1
NVIDIA AI0 NVIDIA AI-1
NVIDIA AI DEVELOPER0 NVIDIAAIDev-1
NeoCortexAI24582053.911471959 nCORAI-1
Neura0 NEURA-3
NeuralAI0 NEURAL-3
Neuro Farms0 NEUROFARMS-3
Neuro_DividendTracker0 Neuro_DividendTracker-2
New BobCoin0 BOB-2
NinetiesCup0 JAZZCUP-3
Nitefeeder0 NITEFEEDER-3
NoFace0 NOFACE-2
Not Coin0 NOT-1
Not Gonna Lie0 NGL-3
Nuron AI753533.910935544867918151 NURON-1
ONERING0 RING-2
OPEN AI0 OPNA-1
Omni0 OMN-3
OmniGrok0 OMNIGROK-2
Ordible0 ORB-3
PAWS0 PAWS-3
PINKMAN0 PINKMAN-3
Pandorabox0 PBOX-3
Paragons DAO Token0 PDT-2
PePe1618009687.915027833 ペペ-1
PeiPei in a memes world0 PEIPEIEW-2
Pepe0.000000000117086205 PEPE-2
Pepe Baby.0 PEPEBABY-1
Pepe Cash0 PepeCash-2
Peppe1482983809738.725127427 PEPPE-1
Pochi Inu0 POCHI-3
QEQE0 QEQE-2
QSTAR0.000000001 Q*-2
QUBY0 QUBY-2
ROKO0.00000000197017508 ROKO-2
ROSS0 ROSS-1
RPG0 RPG-5
RUNodE0 RUDES-6
RWA Tensor0 R-TENSOR-2
Resemble AI0 RESEMBLE AI-1
Rizz Cat0 RIZZ-1
Robin Hood ERC30765012.176013297 RobinHood-2
Ron Desantis122944961.101339914 DESANTIS-1
SAINT0 SAINT-2
SAM0 SAM-3
SELENA INU76458369356.711259635 SELENA-3
SHIA0 SHIA-2
SIGRID0 SIGRID-2
Sadge0 SADGE-2
Sam Altman0 ALTMAN-2
Sam Altman10337298.964426734 SAM-1
Samsung Toshiba Nakamichi Motorola15862269.591778356 SATOSHI-1
Satoshi Nakamoto6976443.877288862 SATOSHI-1
Scuti7500000 SCUTI-1
Shazam AI0 $SHAZAM-2
ShibaHub0 ShibaHub-2
Shibafia545622.818286682 SHIBAFIA-2
Shibafia4590437189.339173434807658711 SMAFIA-1
Shinigami44800.962003363 EYES-1
Shinjurai44887.469470974 SHINJURAI-2
Shinjurai Inu9085637893.73195765 $SHJRI-1
Shinshib617095563272276950539.950674717 SHINSHIB-1
Shumo.io78.679029474 SHUMO-5
SpyBot0 $SPY-3
Squid Grok0 SquidGrok-1
Stax Protocol0 STAX-2
StudioAi0 SAI-2
Super Doge0 sDOGE-2
Super Pepe0 sPEPE-2
Super Shiva0 sSHIVA-2
SuperMarioPorsche911inu0.000515362614512012 SILKROAD-2
Syntensor449506.817232865 STAO-1
Synthrone7500000 SYRNE-1
TAO.ECO490940.625450987 TAOECO-1
THE BOY WHO SAVED CRYPTO2273334 SMINEM-3
TIDEPOD255672.30047843 TIDE-1
TRIFARM_DividendTracker0 TRIFARM_DividendTracker-2
TRUMPIG0 TRUMPIG-1
TUBES0 TUBES-1
Tatsutama8895890737.649601707 Tatsutama-1
Tesla0 TSLA-2
Tesla AI0 TESAI-1
The Balkan Dwarf0.000000002437831352 Kekec-2
The God of Pumps0 ZENDOR-2
The Godfather0 GODFATHER-3
The Holy Bible0 HolyBible-3
The Purge0 PURGE-2
ThunderVerse0 THUNDER-2
Tiger King Inu0 TKINU-4
Tiger King Inu2630908970.437495162546161702 TigerKing-1
Tigger0 TIGG-3
TriFarm Seed Capital0 TRIFARM-3
Troll 2.00 TROLL2.0-2
Trollolol0 TROLL-2
UPMAX0 MAX-6
Universal Intersubjective Work Token0 EIGEN-3
VERTEX0 VTX-2
Vader0 VADER-2
Venom0 VNM-3
VenomTRACKER0 VNMTRACKER-2
Visionize Ai0 VINZ-3
Vitalik Buterin4220396.590129636 VB-1
Vitalik Buterin73664957.340745755 VB-1
Von ShitzinPantz1004145390.383708198 VON-1
Vultr90000 VPU-1
WARIO254925.56975514 WAR-1
Washer35928.015807201 WASH-1
Wen Lunch0 LUNCH-2
What The Fuck0 WTF-2
Wiggum0 WIGGUM-2
Wrapped Ether0 anyETH-2
Wrapped Ether0 WETH-5
X0 X-2
XMOSTAR0 XMO-3
Xunie0 XUNIE-2
YUMA INU0 YUMA-2
Yi He57160210.176365094 HE-1
YoloSwap0.418054701303220042 YOLOSWAP-1
Young Shiva0 ySHIV-2
Zip24280683195790.556725942 ZIP2-1
hammtur0 HAMT-2
iToken93313626935.25033655277656241 iToken-1
niggerbut5961685175741.329824095 niggerbut-1
porkwifhat0 porkwifhat-1
sonic coin0 SONIC-2
the Purge0 PURGE-2
Ÿ0 YAI-5
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⡇⠀⠀⠀⠀⠔⡆⢿⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡃⠀⠀⠈⠀⠀⠁⢸⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢰⠁⠀⠀⠀⠀⠀⠀⢸⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⢀⡠⣼⡆⡄⢀⠃⠀⢸⠀⡀⡇⠂⠤⣀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⢠⠊⠁⠀⣼⠡⠇⢻⠀⢠⠸⡄⡇⢹⠀⠀⠈⢳⡀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⢀⠀⢀⢢⡇⢦⠀⣸⡀⢰⠀⣷⣷⠈⣇⠀⠀⢸⠇⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠈⣆⣼⡿⠤⣼⣠⣏⣇⣼⣶⣹⣾⠧⠼⢦⣀⡿⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⡠⠞⠁⠀⠀⠀⠀⠙⠹⢿⠋⠁⠀⠀⠀⠀⠉⠣⡀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⣠⠎⠀⠀⠀⠀⠀⠀⠀⠀⣠⣿⡀⠀⠀⠀⠀⠀⠀⠀⠈⢢⢄⠀⠀⠀ ⠀⠀⢀⣾⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⣿⣿⡗⠀⠀⠀⠀⠀⠀⠀⠀⢸⠈⢢⠀⠀ ⠀⢠⠃⢿⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⡏⠉⣁⠀⠀⠀⠀⠀⠀⠀⠀⢸⠄⠀⢡⠀ ⠀⣼⠀⠸⡇⠀⠀⠀⠀⠀⠀⠀⠀⣼⠐⣦⢹⣆⠀⠀⠀⠀⠀⠀⠀⣼⠀⠀⠀⡄ ⠀⣿⠀⠀⢷⠀⠀⠀⠀⠀⢀⡀⢀⡏⠀⣿⠀⡏⠑⠀⠀⠀⠀⠀⠀⣼⠀⠀⠀⠃ ⠀⢹⡆⠀⠸⡄⠀⠀⠀⠀⠀⠀⠙⣷⠀⣗⢠⡿⠛⠁⠀⠀⠀⠀⢈⡇⠀⠀⢀⠀ ⠀⠀⢿⠀⠀⢿⠀⠀⠀⠀⠀⠀⠀⠙⣷⣿⡿⠁⠀⠀⠀⠀⠀⠀⢸⡇⠀⢀⡎⠀ ⠀⠀⠘⣇⠀⠘⣇⠀⠀⠀⠀⠀⠀⠀⣿⣽⡇⠀⠀⠀⠀⠀⠀⢰⡿⠀⢀⡞⠀⠀ ⠀⠀⠀⠹⡇⠀⠸⣆⡀⠀⠀⠀⠀⠀⣿⣿⡆⠀⠀⠀⠀⠀⢰⣿⠃⠀⣼⠃⠀⠀ ⠀⠀⠀⠀⢿⣦⠀⠹⣆⠀⠀⠀⣀⣤⣿⣿⣷⣄⠀⠀⣀⣴⣿⡧⣀⣼⡏⠀⠀⠀ ⠀⠀⠀⠀⠸⣿⣷⣿⣿⣷⣶⣿⣿⣿⣿⣿⣿⣿⣶⣶⣿⣿⣿⣿⣿⣿⡇⠀⠀⠀ ⠀⠀⠀⠀⠀⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠁⡇⠀⠀⠀ ⠀⠀⠀⠀⠀⡿⢹⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⢠⡇⠀⠀⠀ ⠀⠀⠀⠀⠀⢁⢸⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠀⡇⠀⠀⠀ ⠀⠀⠀⠀⠀⢸⢸⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠀⡇⠀⠀⠀ ⠀⠀⠀⠀⠀⢸⣼⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡏⠀⡇⠀⠀⠀ ⠀⠀⠀⠀⠀⢸⣿⣿⣿⣿⣿⢻⣿⣿⣿⠏⣿⣿⣿⡟⠻⣿⣻⣿⡇⢰⠇⠀⠀⠀ ⠀⠀⠀⠀⠀⢸⣿⣿⣿⣿⣷⣼⣿⣿⣿⠀⣿⣿⣿⡇⠀⢹⣿⣿⣠⣿⠀⠀⠀⠀ ⠀⠀⠀⠀⢀⣿⣿⡇⣿⣿⣿⣿⣿⣿⣿⠀⢿⣿⣿⣇⣀⢸⣿⣿⣯⠇⠀⠀⠀⠀ ⠀⠀⠀⠀⠈⢻⣿⠇⣿⣿⣿⣿⣿⣿⡇⠀⠸⣿⣿⣿⣯⢸⣿⡷⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⡾⡏⠀⣿⣿⣿⣿⣿⣿⠁⠀⠀⢻⣿⠿⠃⠐⢻⡇⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠈⠀⠁⠀⢸⡏⠁⠀⠹⣿⠀⠀⠀⠘⡇⠀⠀⠀⢨⡇⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠇⠀⠀⠀⠻⠀⠀⠀⠀⢷⠀⠀⠀⢸⠁⠀⠀⠀⠀⠀⠀ ⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠚⠓⠒⠒⣒⣒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒⠒0 PUSSY-2
⠀⠀⠀⠀⠀🟧🟧⠀⠀⠀🟧🟧 ⠀⠀⠀⠀⠀🟧🟧⠀⠀⠀🟧🟧 🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧 🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧 🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧 ⠀⠀⠀⠀⠀🟧🟧🟧⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀🟧🟧🟧 ⠀⠀⠀⠀⠀🟧🟧🟧⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀🟧🟧🟧 ⠀⠀⠀⠀⠀🟧🟧🟧⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀🟧🟧🟧 ⠀⠀⠀⠀⠀🟧🟧🟧⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀🟧🟧 ⠀⠀⠀⠀⠀🟧🟧🟧⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀🟧🟧 ⠀⠀⠀⠀⠀🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧 ⠀⠀⠀⠀⠀🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧 ⠀⠀⠀⠀⠀🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧 ⠀⠀⠀⠀⠀🟧🟧🟧⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀🟧🟧🟧 ⠀⠀⠀⠀⠀🟧🟧🟧⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀🟧🟧🟧 ⠀⠀⠀⠀⠀🟧🟧🟧⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀🟧🟧🟧🟧 🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧 🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧 ⠀⠀⠀⠀⠀🟧🟧⠀⠀⠀🟧🟧 ⠀⠀⠀⠀⠀🟧🟧⠀⠀⠀🟧🟧0 ₿-2
⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬛️⬜️⬜️⬛️⬛️⬛️⬛️⬜️⬜️⬛️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬜️⬜️⬛️⬛️⬜️⬜️⬛️⬛️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬜️⬜️⬜️⬜️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬛️⬛️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️⬜️0 Ξ-2
以太坊0 以太币-2
ContractTokensTransfers#
StakeEther.net1 Airdrop of ID 01
getETH.org1 Airdrop of ID 01
0xD4416b13d2b3a9aBae7AcD5D6C2BbDBE256864011

Transactions

ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
250000 # banana-gun.app-
0xA420872a164644469C6a5dA5C1B2740FD3f13667
 
0.078383061347767009 ETH202.75 USD192.77 USD
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
0.2 ETH517.34 USD491.86 USD
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
4097568560.31100022 BRAI-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
3962351.82981345 RESEMBLE AI-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
1497568560.31100022 Azure AI-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
219914847.66451675 NVIDIA AI-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
4558458.08993709 Gamegptofficial-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
2097568560.31100022 OPNA-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
3397568560.31100022 MisAI-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
596693427.08866228 RIZZ-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
178915474.9234382 NVIDIAAIDev-
0xA420872a164644469C6a5dA5C1B2740FD3f13667
 
0.014 ETH51.34 USD34.43 USD
0xA420872a164644469C6a5dA5C1B2740FD3f13667
 
0 ETH0.00 USD0.00 USD
0xA420872a164644469C6a5dA5C1B2740FD3f13667
 
0.1 ETH366.68 USD245.93 USD
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
1482983809738.725127427 PEPPE-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
36546815.57332073 TSLA-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
26683740682.56503146593000655 PEIPEIEW-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
1085604057.43521519 TSLA-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
22397568560.31100023 FATHER-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
35740682650.462859363010065506 PEIPEIEW-
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
1023975685.60311 TESAI-
0xA420872a164644469C6a5dA5C1B2740FD3f13667
 
1 ETH3679.38 USD2459.31 USD
ERC20 Token Transfers
 
0xA420872a164644469C6a5dA5C1B2740FD3f13667
5622214639.50352849502659606 QEQE-
0xA420872a164644469C6a5dA5C1B2740FD3f13667
 
0 ETH0.00 USD0.00 USD
ERC20 Token Transfers
0xA420872a164644469C6a5dA5C1B2740FD3f13667
 
249545.174055096 QUBY-
0xA420872a164644469C6a5dA5C1B2740FD3f13667
 
0 ETH0.00 USD0.00 USD