Ethereum Explorer
Blocks
Status
Address
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0.
000
136
688
056
029
ETH
Confirmed
Balance
0.
000
136
688
056
029
ETH
Transactions
1
507
Non-contract Transactions
1
495
Internal Transactions
0
Nonce
1493
ERC20 Tokens
394
Contract
Quantity
Value
Transfers
#
$ tLINK
181.
95
Get LINK: https://LINKToken.io
1
$E
160
000
$E
1
00X0 DG-N
2
581
156
.
142
458
659
826
280
978
XDGN
1
0xCHAN
46
456
914
561
.
249
090
909
090
909
091
0xCHAN
1
0xDegenClub
0 DC
4
0xDeploy
0 0xDeploy
3
0xGP4.ai: AI Smart GPT-4 Auditor
2
999
999
0xGP4
1
0xLeverage.ai
0 0xL
3
0xOpen
0 0xO
3
0xREKT
13
930
000
0xREKT
1
0xToolbox
10
289
.
459
125
924
059
028
834
xTOOL
1
4PEPE
7
116
042
510
425
.
097
9
4PEPE
1
9GAG
0 9GAG
3
A Shortfall of Gravitas
749
999
.
25
Gravitas
1
AMA
20
000
AMA
1
AMC
0 AMC
2
AMC
0 AMC
2
AYXOART
0 AYXO
3
Abracadabra
582
665
742
155
.
149
958
537
808
160
169
ABRCDBRA
1
AgilityTools
555
598
AGILITY
1
Albert Peinstein
1
600
000
PEINSTEIN
1
Alien Life Form
0 ALF
3
Anonymous Individuals
0 AI
2
Ape Season
0 APESZN
3
Apollo
0 APOLLO
2
ApΩllΩ
1
600
000
ApΩllΩ
1
Arbitrum Classic
0 ArbC
2
Astaghfirullah
0 Astaghfirullah
3
AustisticIdiotsDivedends
4
989
238
.
956
427
943
AIDS
1
BENIS
0 BENIS
2
BINANCEPIZZA
0 BNBPIZZA
3
BITDOGE
0 BITDOGE
3
BLACK PEPE
0 BEPE
2
BLACKROCK
0 BLACK
5
BOBATEA
0 BT
2
BOOM BOOM
0 BOOMBOOM
3
BROKIE
0 BROKIE
2
BRRRR
64
349
999
.
999
999
993
5
BRRRR
1
Baby Doge 2.0
0 BABYDOGE2.0
3
Baby Generational Wealth
0 BabyGEN
2
Bank of China
0 BOCI
3
Bart Simpson
0 BART
2
Bella
0 BELLA
3
Bella
5
889
660
000
000
BELLA
1
Ben10
0 BEN10
2
Bender
17
910
000
Bender
1
Bert
32
832
BERT
1
Bestial AI
0 BESTAI
3
Billy Token
0 BILLY
4
Bitcoin Red
0 BTCRED
3
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.
15
000
BITCOIN
1
BitcoinTradingSystem
30
216
.
247
020
331
BTS
2
Bitpepe
0 BITPEPE
3
BlockRemit
0 REMIT
3
BlockSocial
0 $BSOCIAL
3
Blockbuster
0 BLOCK
2
Blue Doge
0 BDOGE
2
Bored
20
000
BORED
1
Bot Father
19
806
.
921
951
22
BOF
1
Boxxy
169
150
000
Boxxy
1
BrokeInvestorsTakingChancesOnIncredibleNonsense
0 XBT
3
Buy The Fucking Dip
0 BTFD
2
CHN
0 CHN
2
CSS AI
0 CSS
3
CULT of PEPE
1
520
000
CULTPE
1
Caishen888
5
726
526
.
141
935
483
943
272
131
888
1
CatCoin
0 $CATS
2
Censored
15
295
090
.
733
861
311
Censored
1
Chad
19
999
.
999
999
999
CHAD
1
Chadder
0 CHAD
2
Chef Pee Pee
0 $PEEPEE
3
Chernabog
8
000
CHERNA
1
Chou coin
8
910
000
$CHOU
1
Chronos
0 Chronos
2
Chubby Musk
0 CMU
3
Clyde Frog
5
244
000
000
CLYDE
1
Computer Reaction Faces
0 CRF
2
ConanCoin
0 CONAN
2
CryptHOEs
8
089
.
751
483
469
SLUTS
1
CultOfWagmi
0 $COW
3
D AND G
0 DnG
2
DESERT FOX
0 FOX
2
DOGIE
0 DOGIE
2
DOINKER
721
564
611
.
897
641
189
DOINKER
1
DOODLERS
0.
029
999
999
$DOODLERS
1
DOUCHEBAG
80
000
000
$DOUCHE
1
DUCK
0 DUCK
2
Degen
15
999
.
2
DEGEN
1
Dejitaru Apollo
16
745
850
APOLLO
1
Dejitaru Pepe
15
293
704
.
219
884
473
689
348
271
ǝdǝd
1
Democratic Republic of Jeetistan
0 JEETISTAN
2
Dillon
0 DILLON
3
Discord Search Engine Bot
6
494
400
DSE
1
Doge Degen
11
915
618
.
089
143
DOGEN
1
DogeGram
75
490
.
285
588
235
294
117
647
DG
1
DogeNetwork
0 DGNW
3
DogeOriginalGangsters
91
989
.
222
220
774
DogeOG
2
Dragons Land
0 LAND
3
Dream Team
1
018
484
.
601
477
909
215
190
583
TEAM
1
Drever Inu
0 DRE
3
Druk: Thunder Dragon of Tibetan
7
426
451
.
612
903
226
DRUK
1
Dubai Coin
0 DUBAI
2
ETHEREUMS Consensus
18
000
000
ETHCON
1
Early
0 EARLY
2
Early
0 EARLY
2
EcoGuardian Bot
633
600
000
EGB
1
Eeyore
0 EEYORE
2
Eliza AI Pad
0 ELIPAD
3
ElonDogeYodaSpongebob420Inu
0 MEMECOIN
3
ElonPad
0 EPAD
2
Elons Dragon
0 DragElon
3
Elons Nasty Dog
0 YORKIE
3
EtherealPal
3
000
000
000
EPAL
1
Ethereum 2.0
0 ETH2.0
3
Ethereum Cash
22
977
670
605
.
508
571
428
571
428
572
ETH2.0
1
Eureekas Castle
0 EUREEKA
2
Evolve Chain
0 EVOCHAIN
2
FALKKY
0 FLKKY
3
FANTASY
0 FAN
2
FART
15
840
FART
1
FIFI
0 FIFI
2
FINK Token
0 FINK
3
FRENDS LAMBO
0 FRENS
2
FUD FOMO SAKE
0 FFS
2
FUTURAMA
0 FUT
3
Fak coin
0 FAK
2
Fear of missing out
0 FOMO
2
Figure 01
0 F01
2
Fishmarket
0 TSUKIJI
2
Flare
630
652
.
777
777
777
777
777
778
FLARE
1
Floki 2.0
0 FLOKI2.0
3
Flork
6
394
891
.
885
497
000
87
FLORK
1
Freedom
0 Freedom
3
Fren
0 Fren
2
Fuck BEN
1
500
000
FkBEN
1
Fuck U Dev
0 FUD
2
FudFuckers
281
520
000
FUD
1
Fuel X
0 FUELX
3
Funny Doge
209
761
.
076
818
63
DOGER
2
Future Doge
518.
500
370
24
FUDOGE
3
GAMBLX
0 GAMBLX
3
GDFAM
0 GDFAM
2
GERO-GERO
8
371
731
000
000
Gero
1
GMFREN
23
920
000
.
000
000
004
GMFREN
1
GOD IS GOOD
0 GIG
2
GOOBY
20
000
000
$GOOBY
2
GOOFY
1
980
GOOFY
1
Galactus
8
000
000
000
GALACTUS
1
Geneartional Wealth 2.0
38
650
492
061
.
543
225
806
451
612
903
GEN2.0
1
Genesis 2.0
1
814
653
.
793
333
333
333
333
334
GENESIS2.0
1
Genesis Generation
1
691
500
GeGe
1
Gentlemen
0 SPY
2
George Washington
0 NOTHING
2
GiraffeScene
0 Giraffe
3
Godzilla
0 ZILLA
2
Good Fucking Morning
0 GFM
2
Good Fucking Morning
1
167
135
000
GFM
1
Good Fucking Night
15
920
GFN
1
Good profit finally
0 GPF
2
Graph
0 GRAPH
2
Grilled Cheems
0 GRLCHMS
3
Groot
0 GROOT
5
HADES
0 HADES
3
HALF ELON MUSK
0 MUSK0.5
2
HATAMOTO
0 HATAMOTO
2
HE
6
900
000
000
SAM
1
Hacker
0 HACKER
5
Hacker_Dividend_Tracker
0 Hacker_Dividend_Tracker
3
Happy Father's Day
0 FATHERS
2
Harambe
0 HARAMBE
2
Harry Potter
19
900
000
PPOTTER
1
HarryPotterObamaPepe1Inu
0 PEPE
8
Have Fun Staying Poor
0 HFSP
3
Heads or Tails
0 FLIP
7
Hello world
19
599
999
.
72
HELLO
1
Hinata Hyuga
0 HINATA
4
Hodlzilla
0 HZILLA
3
Hoe Hoe Hoe
15
000
000
HOEHOEHOE
1
Hogwarts Pepe
139
293
604
.
719
09
PEPEZAR
1
Holy ETH
0 Holy
3
Honda Civic
6
453
135
.
267
903
CIVIC
1
I LOVE YOU
0 MOMMY
2
I am Rekt. I ape and it dumps. I sell and it pumps. I fomo the top , I sell the bottom. I left a moonbag, dusted. I sold all my bag, it pumps to milly . Am i cursed? All the devs turn tax to 99 whenever i buy. I am REKT.
0 REKT
2
ILU
16
915
ILU
1
Innovatix
275
200
000
IVX
1
Inshallah DAO
6
278
798
250
000
INDAO
1
Insid0r
0 Insid0r
2
Insomniacs
0 SLEEP
3
International Meme Fund
8
222
215
.
530
645
161
IMF
1
JERRY
0 JERRY
2
JESUS
5
445
014
842
055
.
872
721
006
T-REX
1
JPMorgant
0 JPM
2
Jamal
990 JAMAL
1
Jeffe
0 JEFFE
3
JustAnotherEgg
0 EGG
3
Justin Sun
0 JUSTIN
2
KINGPEPE
0 KINGPEPE
2
Kabosu
0 KABOSU
3
Keyboard Cat
0 KCAT
3
Kiki
2
384
000
$KIKI
1
Kim Kardashian
0 KIMK
2
Kingsman Coin
0 Kingsman
2
Kirby
0 Kirby
2
Kitties
0 KTS
3
Kitties
1
747
155
.
611
592
825
KTS
1
Know Your Customer
0 KYC
2
Krusty Krab
0 KRUSTY
2
LISP
313
600
Υλ
1
Laszlo Hanyecs
0 Laszlo
2
Laszlo Hanyecs
336
000
LASZLO
1
LiquiShield
0 LiqS
3
Louis Vuitton
0 LOUIV
2
Lumina Bot
700
000
000
LUMINA
1
MATRIX PEPE
0 MP
2
MISSOR
0 MISSOR
3
Make It Bullish
0 BMI
2
Make it
0 MakeIt
2
Manipulated
0 MEDIA
2
McBobo
5
943
929
010
MCBOBO
1
McCZ
2
839
.
097
071
758
6
MCCZ
1
Meme 2.0
14
835
524
.
991
935
484
MEME2.0
1
Meme God
0 MGOD
2
Meme Street Gang
0 MSG
3
MicroFTX 2.0
126.
65
MFTX2
1
Midaddy
15
000
000
DADDY
1
Milhouse Van Houten
0 MILHOUSE
2
Miss Pepe
0 M$ PEPE
3
Miss Wojak
0 MSWOJAK
2
Money Printer
0 BRRR
3
Mong Inu
0 MONGI
3
Mongoose 3.0
6
672
432
.
645
431
057
MONG3.0
1
Monkey Claw
0 MCL
3
Montenegro
0 MONTE
3
My 1st Koin
6
872
579
999
999
.
999
MY1STKOIN
1
NAME
1
980
TICKER
1
NFT Athlete Club
0 NAC
3
Never.
0 NEVER
2
New Community Psyop
0 nPSYOP
2
Nizo Neko
0 Nizo
2
NoFace
0 NOFACE
2
None Trading
0 NONE
3
Normi Finance
0 NRMI
3
Normies
662
400
NORMIES
1
ORWELL
0 ORWELL
3
Octopus Game
52
294
182
.
910
462
260
207
668
145
OCTG
1
OnFire
633
414
.
634
146
341
463
414
634
FIRE
1
OnePiece.place
0 OnePiece
2
PEPE ASTRONOMY
0 PA
2
PEPE CLASSIC
5
731
.
930
329
656
860
539
055
PEPEc
1
PEPE OG
0 POG
2
PEPECOIN
0 PEPECOIN
2
PEPETH
0 PEPETH
2
PICCOLO JUNIOR
0 Piccolo
2
PIZZAPE
1
600
000
PIZZAPE
1
PLACE ON BLOCKCHAIN
708
222
.
656
25
PLACE
1
POND BOT
4
780
975
.
609
756
097
PNBT
1
PUCCA
820
934
.
764
523
630
513
260
313
PUCCA
1
PUNCH COIN
13
884
919
.
838
709
678
PUNCH
1
Paradigm
8
499
.
15
PARADIGM
1
Patek Pepe
0 PETEK
2
Pei Pei 2.0
0 PEIPEI2.0
2
Pekachu
92
555
.
555
555
56
PEKACHU
1
PengyX
20
629
288
.
720
697
419
550
554
784
PENGYX
1
Pepalisa
159
999
.
2
PEPALISA
1
Pepe
3
500
000
PEPE
1
Pepe BTC
315
000
PepeBTC
1
Pepe Dot Doom
1
990
000
PPDD
1
Pepe Lore
0 PELO
3
Pepe Ordinal Vision
0 POV
2
Pepe Planet
0 Planet
2
Pepe Rocket
15
920
000
000
PEPEROCKET
1
Pepe The Penguin
6
345
975
.
609
756
097
498
780
488
PENGU
1
Pepe Uchiha
0 PEPUCH
3
Pepe VS Jeets
1
665
932
400
PEJE
1
Pepe and Wojak
0 PEJAK
2
PepeLego
0 LEGO
6
PepeParody
3
891
.
923
774
863
pepe
1
Pepenaut
0 PEPAUT
3
Peponzi
0 Peponzi
3
Perc 30
297
000
000
PERC
1
Philosoraptor
0 PRAP
2
Pig's House
20
000
Skulls
6
Planet Nine
0 P9
2
Popo the Robot
440
946
.
531
219
512
POPO
1
PrickMorty
0 PRICK
3
Print The Ribbit
10
454
.
544
PR
1
Print Wojak
1
343
747
.
332
049
141
Brrr
2
Psyduck
714
999
999
999
.
999
22
PSY
1
Psyop Classic
0 PSYOPC
2
PulseMoon
15
920
PulseMoon
1
Quanto sei bella Roma
0 ROMA
2
REAPER
0 REAPER
3
RICK
0 RICK
2
Red Pill
0 PILL
2
Richie
14
925
000
RICHIE
1
Roadman Pepe
0 SLANG
2
Rock
2
000
000
000
ROCK
1
Rock
2
008
028
.
039
130
178
160
753
77
ROCK
2
RonWeasleyGenslerSpyro11Inu
0 ETH
3
Rutkowski
580
634
999
.
999
999
915
RUTKOWSKI
1
RyoshiOriginalVision
0 ROV
2
SHIPEPE
0 SPEPE
2
SHIRO 正式
0 SHIRO
2
SILK ROAD
0 SILK
3
SOPRANO
0 TONY
2
SOYJAK
0 SOYJAK
2
SWAGMI
0 $SWAGMI
2
SWAPX
1
600
000
SWAPX
1
Sadge
0 SADGE
2
SatoshiOriginalVision
0 SOV
2
Saudi Coin
0 SAUDI
3
SaudiDoge
0 SDOGE
2
Sendor
0 SENDOR
2
Shakana Inu
0 Shakana
2
Shaun Inu
0 SHAUN
2
Shazam AI
0 $SHAZAM
2
Sheesh
1
499
999
.
25
SHEESH
1
Shib Infinity
87
092
383
.
213
146
937
SHIB∞
1
ShibNet
0 SNET
3
ShibVerseAI
0 SVAI
3
Shiba Wash
449.
99
WASH
1
ShibariumOriginalVision
19
691
148
.
514
95
SHIBOV
1
Shibber
0 SHIBBER
2
Shinmen Takezo
1
979
999
999
.
1
TAKEZO
1
Shori 勝利
0 yShori
2
Sigma
22
973
652
093
.
957
419
354
838
709
678
SIGMA
1
Smell Token
0 SML
2
Smol Ape
0 SAPE
2
SmugCoin
0 SMUG
2
Snorlax
17
910
000
SNORLAX
1
Solana 2.0
0 SOL2.0
2
Space Monkeyz
0 MONKEYZ
2
Stealth Coin
0 STEALTH
2
Stevoshi
0 BTCAPL
3
Suck My Dick Coin
15
920
SMDC
1
Suck My Dick Coin
0 SMDC
3
THE MEME
43
172
226
.
901
992
023
THEMEME
2
TOPG.Com
0 TOPG
2
TURBONER™ 2.0
0 TRBNR2.0
3
Tates Arch Nemesis
0 AntMan
2
The Box
0 BOX
2
The DogeFather
0 DOGEFATHER
2
The Flintstones
0 FLINTS
3
The Gladiator
0 SPARTA
3
The Godfather
4
500
000
000
GODFATHER
1
TigerKing 2.0
0 TKING2.0
3
Tora Doshi
0 ToShi
2
Torts.gg
0 TORTS
3
TrollfaceAI
0 TROLLAI
2
Trollon Musk
14
925
Trollon
1
Tucker Carlson
0 TUCKER
2
Tweety Bird
2
060
782
071
.
884
388
872
988
955
705
TWEETY
6
Twitter Doge
1
477
574
.
261
212
5
TDOGE
1
Twitter Doge
0 TWOGE
2
Twitter Doge
0 DOGGER
2
Twitter Doge
0 TDOGE
2
UTYA The Duckling
0 UTYA
2
Unidentified Flying Object
0 UFO
3
Unleash The Memes
0 MEMES
2
VALHALLAH
0 VALHALLAH
2
VISION OF THE BOLZ
1
799
999
.
4
VBOLZ
3
VULPINI
0 $VULPI
5
Vertex
0 VTX
2
Virtual AI
0 Virtual
2
Vitalik Memes
0 VITAMEME
3
VitalikBull
0 VIBULL
2
WOJAK OF ALL TRADES
15
840
000
WOAT
1
WOOFZONE
0 WOOF
2
WTF
0 WTF
2
Waifu
0 WAIFU
4
Wall Street Coin
19
900
WSC
1
We're All Gonna Get Her
0 WAGGH
3
Wen Lunch?
0 LUNCH
2
Whale Coin
0 WHALE
2
Where is dev
0 BAHAMAS
2
Wojak & Pepe
0 Wope
2
Wojak Coin
25
424
.
744
751
651
067
074
714
WOJAK
2
Wojak soyjak cat
1
592
000
WSC
1
WojakWojak
20
000
Wojak²
1
World Bee Day
2
000
000
000
BEE
1
YESYESYES
0 YYY
3
Yotsuba Koiwai
0 $404girl
2
ZAZA
3
446
421
385
170
.
871
280
937
136
000
366
ZAZA
1
ZERO
0 ZERO
2
Zero Two
0 02
3
Zero2Hero
0 HERO
2
Zeus Doge
0 ZDOGE
3
diamondpepe
69
000
000
DP
1
epeP
4
339
499
.
366
765
120
8
EPEP
1
good day
0 gd
2
ksuMnolEyaDhtriByppaH
0 NOLEDBPH
2
monky
1
900
000
000
MONKY
1
xD
8
000
xD
1
يللايللا
16
830
LFG
1
Transactions
All
Address on input side
Address on output side
Non-contract
Internal
$ tLINK (ERC20)
$E (ERC20)
00X0 DG-N (ERC20)
0xCHAN (ERC20)
0xDegenClub (ERC20)
0xDeploy (ERC20)
0xGP4.ai: AI Smart GPT-4 Auditor (ERC20)
0xLeverage.ai (ERC20)
0xOpen (ERC20)
0xREKT (ERC20)
0xToolbox (ERC20)
4PEPE (ERC20)
9GAG (ERC20)
A Shortfall of Gravitas (ERC20)
AMA (ERC20)
AMC (ERC20)
AMC (ERC20)
AYXOART (ERC20)
Abracadabra (ERC20)
AgilityTools (ERC20)
Albert Peinstein (ERC20)
Alien Life Form (ERC20)
Anonymous Individuals (ERC20)
Ape Season (ERC20)
Apollo (ERC20)
ApΩllΩ (ERC20)
Arbitrum Classic (ERC20)
Astaghfirullah (ERC20)
AustisticIdiotsDivedends (ERC20)
BENIS (ERC20)
BINANCEPIZZA (ERC20)
BITDOGE (ERC20)
BLACK PEPE (ERC20)
BLACKROCK (ERC20)
BOBATEA (ERC20)
BOOM BOOM (ERC20)
BROKIE (ERC20)
BRRRR (ERC20)
Baby Doge 2.0 (ERC20)
Baby Generational Wealth (ERC20)
Bank of China (ERC20)
Bart Simpson (ERC20)
Bella (ERC20)
Bella (ERC20)
Ben10 (ERC20)
Bender (ERC20)
Bert (ERC20)
Bestial AI (ERC20)
Billy Token (ERC20)
Bitcoin Red (ERC20)
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. (ERC20)
BitcoinTradingSystem (ERC20)
Bitpepe (ERC20)
BlockRemit (ERC20)
BlockSocial (ERC20)
Blockbuster (ERC20)
Blue Doge (ERC20)
Bored (ERC20)
Bot Father (ERC20)
Boxxy (ERC20)
BrokeInvestorsTakingChancesOnIncredibleNonsense (ERC20)
Buy The Fucking Dip (ERC20)
CHN (ERC20)
CSS AI (ERC20)
CULT of PEPE (ERC20)
Caishen888 (ERC20)
CatCoin (ERC20)
Censored (ERC20)
Chad (ERC20)
Chadder (ERC20)
Chef Pee Pee (ERC20)
Chernabog (ERC20)
Chou coin (ERC20)
Chronos (ERC20)
Chubby Musk (ERC20)
Clyde Frog (ERC20)
Computer Reaction Faces (ERC20)
ConanCoin (ERC20)
CryptHOEs (ERC20)
CultOfWagmi (ERC20)
D AND G (ERC20)
DESERT FOX (ERC20)
DOGIE (ERC20)
DOINKER (ERC20)
DOODLERS (ERC20)
DOUCHEBAG (ERC20)
DUCK (ERC20)
Degen (ERC20)
Dejitaru Apollo (ERC20)
Dejitaru Pepe (ERC20)
Democratic Republic of Jeetistan (ERC20)
Dillon (ERC20)
Discord Search Engine Bot (ERC20)
Doge Degen (ERC20)
DogeGram (ERC20)
DogeNetwork (ERC20)
DogeOriginalGangsters (ERC20)
Dragons Land (ERC20)
Dream Team (ERC20)
Drever Inu (ERC20)
Druk: Thunder Dragon of Tibetan (ERC20)
Dubai Coin (ERC20)
ETHEREUMS Consensus (ERC20)
Early (ERC20)
Early (ERC20)
EcoGuardian Bot (ERC20)
Eeyore (ERC20)
Eliza AI Pad (ERC20)
ElonDogeYodaSpongebob420Inu (ERC20)
ElonPad (ERC20)
Elons Dragon (ERC20)
Elons Nasty Dog (ERC20)
EtherealPal (ERC20)
Ethereum 2.0 (ERC20)
Ethereum Cash (ERC20)
Eureekas Castle (ERC20)
Evolve Chain (ERC20)
FALKKY (ERC20)
FANTASY (ERC20)
FART (ERC20)
FIFI (ERC20)
FINK Token (ERC20)
FRENDS LAMBO (ERC20)
FUD FOMO SAKE (ERC20)
FUTURAMA (ERC20)
Fak coin (ERC20)
Fear of missing out (ERC20)
Figure 01 (ERC20)
Fishmarket (ERC20)
Flare (ERC20)
Floki 2.0 (ERC20)
Flork (ERC20)
Freedom (ERC20)
Fren (ERC20)
Fuck BEN (ERC20)
Fuck U Dev (ERC20)
FudFuckers (ERC20)
Fuel X (ERC20)
Funny Doge (ERC20)
Future Doge (ERC20)
GAMBLX (ERC20)
GDFAM (ERC20)
GERO-GERO (ERC20)
GMFREN (ERC20)
GOD IS GOOD (ERC20)
GOOBY (ERC20)
GOOFY (ERC20)
Galactus (ERC20)
Geneartional Wealth 2.0 (ERC20)
Genesis 2.0 (ERC20)
Genesis Generation (ERC20)
Gentlemen (ERC20)
George Washington (ERC20)
GiraffeScene (ERC20)
Godzilla (ERC20)
Good Fucking Morning (ERC20)
Good Fucking Morning (ERC20)
Good Fucking Night (ERC20)
Good profit finally (ERC20)
Graph (ERC20)
Grilled Cheems (ERC20)
Groot (ERC20)
HADES (ERC20)
HALF ELON MUSK (ERC20)
HATAMOTO (ERC20)
HE (ERC20)
Hacker (ERC20)
Hacker_Dividend_Tracker (ERC20)
Happy Father's Day (ERC20)
Harambe (ERC20)
Harry Potter (ERC20)
HarryPotterObamaPepe1Inu (ERC20)
Have Fun Staying Poor (ERC20)
Heads or Tails (ERC20)
Hello world (ERC20)
Hinata Hyuga (ERC20)
Hodlzilla (ERC20)
Hoe Hoe Hoe (ERC20)
Hogwarts Pepe (ERC20)
Holy ETH (ERC20)
Honda Civic (ERC20)
I LOVE YOU (ERC20)
I am Rekt. I ape and it dumps. I sell and it pumps. I fomo the top , I sell the bottom. I left a moonbag, dusted. I sold all my bag, it pumps to milly . Am i cursed? All the devs turn tax to 99 whenever i buy. I am REKT. (ERC20)
ILU (ERC20)
Innovatix (ERC20)
Inshallah DAO (ERC20)
Insid0r (ERC20)
Insomniacs (ERC20)
International Meme Fund (ERC20)
JERRY (ERC20)
JESUS (ERC20)
JPMorgant (ERC20)
Jamal (ERC20)
Jeffe (ERC20)
JustAnotherEgg (ERC20)
Justin Sun (ERC20)
KINGPEPE (ERC20)
Kabosu (ERC20)
Keyboard Cat (ERC20)
Kiki (ERC20)
Kim Kardashian (ERC20)
Kingsman Coin (ERC20)
Kirby (ERC20)
Kitties (ERC20)
Kitties (ERC20)
Know Your Customer (ERC20)
Krusty Krab (ERC20)
LISP (ERC20)
Laszlo Hanyecs (ERC20)
Laszlo Hanyecs (ERC20)
LiquiShield (ERC20)
Louis Vuitton (ERC20)
Lumina Bot (ERC20)
MATRIX PEPE (ERC20)
MISSOR (ERC20)
Make It Bullish (ERC20)
Make it (ERC20)
Manipulated (ERC20)
McBobo (ERC20)
McCZ (ERC20)
Meme 2.0 (ERC20)
Meme God (ERC20)
Meme Street Gang (ERC20)
MicroFTX 2.0 (ERC20)
Midaddy (ERC20)
Milhouse Van Houten (ERC20)
Miss Pepe (ERC20)
Miss Wojak (ERC20)
Money Printer (ERC20)
Mong Inu (ERC20)
Mongoose 3.0 (ERC20)
Monkey Claw (ERC20)
Montenegro (ERC20)
My 1st Koin (ERC20)
NAME (ERC20)
NFT Athlete Club (ERC20)
Never. (ERC20)
New Community Psyop (ERC20)
Nizo Neko (ERC20)
NoFace (ERC20)
None Trading (ERC20)
Normi Finance (ERC20)
Normies (ERC20)
ORWELL (ERC20)
Octopus Game (ERC20)
OnFire (ERC20)
OnePiece.place (ERC20)
PEPE ASTRONOMY (ERC20)
PEPE CLASSIC (ERC20)
PEPE OG (ERC20)
PEPECOIN (ERC20)
PEPETH (ERC20)
PICCOLO JUNIOR (ERC20)
PIZZAPE (ERC20)
PLACE ON BLOCKCHAIN (ERC20)
POND BOT (ERC20)
PUCCA (ERC20)
PUNCH COIN (ERC20)
Paradigm (ERC20)
Patek Pepe (ERC20)
Pei Pei 2.0 (ERC20)
Pekachu (ERC20)
PengyX (ERC20)
Pepalisa (ERC20)
Pepe (ERC20)
Pepe BTC (ERC20)
Pepe Dot Doom (ERC20)
Pepe Lore (ERC20)
Pepe Ordinal Vision (ERC20)
Pepe Planet (ERC20)
Pepe Rocket (ERC20)
Pepe The Penguin (ERC20)
Pepe Uchiha (ERC20)
Pepe VS Jeets (ERC20)
Pepe and Wojak (ERC20)
PepeLego (ERC20)
PepeParody (ERC20)
Pepenaut (ERC20)
Peponzi (ERC20)
Perc 30 (ERC20)
Philosoraptor (ERC20)
Pig's House (ERC20)
Planet Nine (ERC20)
Popo the Robot (ERC20)
PrickMorty (ERC20)
Print The Ribbit (ERC20)
Print Wojak (ERC20)
Psyduck (ERC20)
Psyop Classic (ERC20)
PulseMoon (ERC20)
Quanto sei bella Roma (ERC20)
REAPER (ERC20)
RICK (ERC20)
Red Pill (ERC20)
Richie (ERC20)
Roadman Pepe (ERC20)
Rock (ERC20)
Rock (ERC20)
RonWeasleyGenslerSpyro11Inu (ERC20)
Rutkowski (ERC20)
RyoshiOriginalVision (ERC20)
SHIPEPE (ERC20)
SHIRO 正式 (ERC20)
SILK ROAD (ERC20)
SOPRANO (ERC20)
SOYJAK (ERC20)
SWAGMI (ERC20)
SWAPX (ERC20)
Sadge (ERC20)
SatoshiOriginalVision (ERC20)
Saudi Coin (ERC20)
SaudiDoge (ERC20)
Sendor (ERC20)
Shakana Inu (ERC20)
Shaun Inu (ERC20)
Shazam AI (ERC20)
Sheesh (ERC20)
Shib Infinity (ERC20)
ShibNet (ERC20)
ShibVerseAI (ERC20)
Shiba Wash (ERC20)
ShibariumOriginalVision (ERC20)
Shibber (ERC20)
Shinmen Takezo (ERC20)
Shori 勝利 (ERC20)
Sigma (ERC20)
Smell Token (ERC20)
Smol Ape (ERC20)
SmugCoin (ERC20)
Snorlax (ERC20)
Solana 2.0 (ERC20)
Space Monkeyz (ERC20)
Stealth Coin (ERC20)
Stevoshi (ERC20)
Suck My Dick Coin (ERC20)
Suck My Dick Coin (ERC20)
THE MEME (ERC20)
TOPG.Com (ERC20)
TURBONER™ 2.0 (ERC20)
Tates Arch Nemesis (ERC20)
The Box (ERC20)
The DogeFather (ERC20)
The Flintstones (ERC20)
The Gladiator (ERC20)
The Godfather (ERC20)
TigerKing 2.0 (ERC20)
Tora Doshi (ERC20)
Torts.gg (ERC20)
TrollfaceAI (ERC20)
Trollon Musk (ERC20)
Tucker Carlson (ERC20)
Tweety Bird (ERC20)
Twitter Doge (ERC20)
Twitter Doge (ERC20)
Twitter Doge (ERC20)
Twitter Doge (ERC20)
UTYA The Duckling (ERC20)
Unidentified Flying Object (ERC20)
Unleash The Memes (ERC20)
VALHALLAH (ERC20)
VISION OF THE BOLZ (ERC20)
VULPINI (ERC20)
Vertex (ERC20)
Virtual AI (ERC20)
Vitalik Memes (ERC20)
VitalikBull (ERC20)
WOJAK OF ALL TRADES (ERC20)
WOOFZONE (ERC20)
WTF (ERC20)
Waifu (ERC20)
Wall Street Coin (ERC20)
We're All Gonna Get Her (ERC20)
Wen Lunch? (ERC20)
Whale Coin (ERC20)
Where is dev (ERC20)
Wojak & Pepe (ERC20)
Wojak Coin (ERC20)
Wojak soyjak cat (ERC20)
WojakWojak (ERC20)
World Bee Day (ERC20)
YESYESYES (ERC20)
Yotsuba Koiwai (ERC20)
ZAZA (ERC20)
ZERO (ERC20)
Zero Two (ERC20)
Zero2Hero (ERC20)
Zeus Doge (ERC20)
diamondpepe (ERC20)
epeP (ERC20)
good day (ERC20)
ksuMnolEyaDhtriByppaH (ERC20)
monky (ERC20)
xD (ERC20)
يللايللا (ERC20)
Previous
1
2
3
4
...
61
Next
0x8f6d9043cb764e472f70c52fcfa506763db13eb581ed6f3b6e30ffb004521d9e
mined
210 days 15 hours ago
Transfer
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x39F77e7441cc66BdBA8C273dE4BA94B12901A5Cf
3.
331
771
904
671
081
667
ETH
0x8f35e6734a0250448bd72ea103b6a01ebec8c9b538b0c8be34053478ab68e7ce
mined
210 days 15 hours ago
Transfer
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0xD31f8de347dE55eff0Dc86D6Daf652DC3bbABB4a
2 ETH
0xa89a625fd5e107a456f3419184888855b0899418261211e66d6c76aee7543a67
mined
214 days 16 hours ago
0xfb3bdb41
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
15
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0x6134e39988b5e73267Ce979b64A143e5aaf6422B
0.
099
541
933
950
951
992
WETH
0x6134e39988b5e73267Ce979b64A143e5aaf6422B
0x96157167A5b92fFa244c83de92b8C88f08D903eD
1
500
000
PEPE
0x6134e39988b5e73267Ce979b64A143e5aaf6422B
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
3
500
000
PEPE
0x1ab0effd58eba04d20720a6180afae525529d4a88f878520063b6d3eb57097c0
mined
216 days 21 hours ago
Transfer
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x351ed31Cfed1a951e5Ce4b3ABff6F9B95213E01F
0.
174
315
ETH
0x5a7827446e3ed37510c3bae99d7efdfab1d2b131f0d3b2b282300a6af5f8adee
mined
222 days 21 hours ago
Transfer
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0xFe3d689AB66314E5afA84F2A547DeE505abeB32e
0.
1
ETH
0x7ab624fcf0df3fd908c0d97d0ffe2dc25d42700bd27f8683056eda1af3f29d80
mined
222 days 21 hours ago
Transfer
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x05696CEc584a044680f7B3Acff68e17Bf55EB7bf
0.
1
ETH
0xd6ecb7b6448f27bdc38972a5495c5a22b5cf4f85b970b64718abd9d8e39ebd8b
mined
222 days 21 hours ago
Transfer
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x484715Abd36678FBF8835e00Bb43877e836db6D8
0.
1
ETH
0xeb952aed3e139cd57dc54fd9a7de3dcb92975c1f5449130e345191a9be5ce07d
mined
222 days 21 hours ago
Transfer
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0xC52ACaEA66790943A4DD83CfF80eeC915D3d8Ae9
0.
1
ETH
0x04537f1cbf7aa0664f9b8b7ee70ded4819eda124e0a7fa7fd9b7619007720c75
mined
222 days 21 hours ago
Transfer
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x40aB6fD56064339f2DCfAad1B9ACF76d74961755
0.
1
ETH
0xf1749712d9652adf4a67efee0b7d38dc76ffef35f317bdafa119bb6909cea9a3
mined
222 days 21 hours ago
Transfer
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0xfFEA5DC95A41855Ea51A2274F1291229a0eacC37
0.
1
ETH
0xe552737e93f1e244cf9e863c832d0dfa9079b0ea7f17c126bfed2448699c818e
mined
232 days 18 hours ago
0x3593564c
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD
0.
01
ETH
ERC20 Token Transfers
0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD
0xfb4BF444C25B063560D2E96c072D36307571413A
0.
01
WETH
0xfb4BF444C25B063560D2E96c072D36307571413A
0x89Ea56FED4D680038Ea8a05667bC355c83dBF8A1
7
288
531
.
433
309
506
DOINKER
0xfb4BF444C25B063560D2E96c072D36307571413A
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
721
564
611
.
897
641
189
DOINKER
0xbb1e4e042e79b275034d0dfdf6612a1445781cda0a81937f59bb6320a7f87199
mined
241 days 20 hours ago
0xfb3bdb41
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
134
872
905
676
737
66
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0xa44a7440BC4Fb15296D6e1128eFeF0257F851BfF
0.
125
635
899
148
838
572
WETH
0xa44a7440BC4Fb15296D6e1128eFeF0257F851BfF
0xfA69B66aac285571B0b65772c6544EDf0e6b0123
16
827
600
PEJE
0xa44a7440BC4Fb15296D6e1128eFeF0257F851BfF
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
1
665
932
400
PEJE
0xca2824ecf5573058cceee93ddf8e58213a8d62f0a2f7da4cb8f5a25e8b4339ce
mined
242 days 20 hours ago
0xfb3bdb41
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
15
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0x1C7999C0dAB5086fEE9a92a5E2965c1f8277A60D
0.
057
738
553
188
637
128
WETH
0x1C7999C0dAB5086fEE9a92a5E2965c1f8277A60D
0x000000000000000000000000000000000000dEaD
1
960
885
.
273
170
73
BOF
0x1C7999C0dAB5086fEE9a92a5E2965c1f8277A60D
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
19
806
.
921
951
22
BOF
0x8ee0149e2519ca592b484618150d02d4830eedc0991dee816399dcd58245180c
mined
242 days 23 hours ago
Failed
0xfb3bdb41
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
079
167
073
170
731
71
ETH
0x69bc1728fe66ea4920a9e72d815b271285444b11e1926318124b159ee8db588b
mined
243 days 20 hours ago
0xfb3bdb41
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
145
512
195
121
951
23
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0xAAb56Bd002d76c3C4d7057109d8D8F89ae78ddF6
0.
016
671
529
484
536
83
WETH
0xAAb56Bd002d76c3C4d7057109d8D8F89ae78ddF6
0x3e1ba5e268d0EC472b8dEaB709DC6Eec66C1E3E6
271
463
.
414
634
146
341
463
414
FIRE
0xAAb56Bd002d76c3C4d7057109d8D8F89ae78ddF6
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
633
414
.
634
146
341
463
414
634
FIRE
0xfd92bb15436c8e6c354fe13f9913ad15397b1685ef8aed83c6b68b00739319e3
mined
243 days 21 hours ago
Failed
0xfb3bdb41
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
110
871
475
609
756
1
ETH
0xe5def71119c561fbff8fc8f7d639eb08ae0f8b765363643650d40e7a4b5bc528
mined
244 days 16 hours ago
Failed
0xfb3bdb41
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
15
ETH
0xfe8b41b1e1832a2303b7956d86190fc252e2d92fca8544932e68ce7200b223e9
mined
244 days 18 hours ago
Failed
0xfb3bdb41
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
051
480
487
804
878
05
ETH
0x31e29ca51c955cc3410ac7b2780348ef070b94c244e865e7116fa2c024600585
mined
245 days 16 hours ago
0xfb3bdb41
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
15
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0x41d381E9439e018bd845581d14CEe538d3BCb49f
0.
013
547
738
699
521
421
WETH
0x41d381E9439e018bd845581d14CEe538d3BCb49f
0xE284e58010C42f2203c9b112C43D570a3aFDc65a
20
067
.
037
941
176
470
588
235
DG
0x41d381E9439e018bd845581d14CEe538d3BCb49f
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
75
490
.
285
588
235
294
117
647
DG
0xab880c92ed35eedee8b44192246cb657c27e1e04d90fc7078205c3fbb9192a09
mined
245 days 17 hours ago
Failed
0xfb3bdb41
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
097
323
529
411
764
7
ETH
0x13d8021cfdd61a8ccfdea3855801411df5237007164d7aaca3e91094fae0acaa
mined
245 days 22 hours ago
0x095ea7b3
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x4afbcF4Ac33A865e4Cbd29E9B8b7AaD327898684
0 ETH
0xea759e756116c4b148d47dbedbdadbc45e3e3806ef6ca2f32370293b6e0a904d
mined
245 days 22 hours ago
0x0162e2d0
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x58dF81bAbDF15276E761808E872a3838CbeCbcf9
0.
5
ETH
ERC20 Token Transfers
0x58dF81bAbDF15276E761808E872a3838CbeCbcf9
0xfB46531ABe710D7fA2521Dc55caD12ad73BDC996
0.
188
385
WETH
0xfB46531ABe710D7fA2521Dc55caD12ad73BDC996
0x4afbcF4Ac33A865e4Cbd29E9B8b7AaD327898684
1
085
752
.
037
931
443
134
239
725
PENGYX
0xfB46531ABe710D7fA2521Dc55caD12ad73BDC996
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
20
629
288
.
720
697
419
550
554
784
PENGYX
0xe7d89dc7c7f74058c1ffeff85e87b109650ab87b4805125754095e426193afa2
mined
246 days ago
Failed
0xfb3bdb41
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
094
705
882
352
941
18
ETH
0x524fb285d60e7339853d4771b6ee88b6743b312ff98dd56bca5b741c124dae84
mined
246 days 16 hours ago
0xfb3bdb41
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
156
768
321
163
460
22
ETH
ERC20 Token Transfers
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0x57C5FE3eb8A7bB0a614D0a4Da920f60985b9084B
0.
013
609
737
985
956
846
WETH
0x57C5FE3eb8A7bB0a614D0a4Da920f60985b9084B
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
708
222
.
656
25
PLACE
0x1d6bc45030265478c5eb45855d6be928c3f71cb9071a797b8bd6a9e07e6e931b
mined
247 days 1 hour ago
Failed
0xfb3bdb41
0xbEf5CbA93561BC084e8aa5db37DC1265998Ae131
0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D
0.
099
558
823
529
411
76
ETH
Previous
1
2
3
4
...
61
Next