memoscan

0x32e7…656f

All memos sent from and to 0x32e7…656f.
0x2857ad7c…7168sent to0x32e7851f…656f·#15,885,245·0x6ea3d06d…0f850b
This fucktard fudding really needs to get a life, its locked and renounced you inbreed retard ! There's no hidden mint, even if there was there's nothing dev can do now asshole . At least you could come up with a better fake excuse like Idk, dev bought 20 wallets ! What a loser, even going to the lenght of making posts on twitter fudding lol .
0xe51b05ae…1cccsent to0x32e7851f…656f·#15,885,003·0xe4bd7a94…2b9ef4
193: uint256 private _maxLimit = ~uint256(0); This sets the value of the variable _maxLimit to the maximum uint256 number available, which ends up being: uint256 private _maxLimit = 115792089237316195423570985008687907853269984665640564039457584007913129639935; hidden mint Line 255: _balances[0x48123D61e870142659aeEB1f0BC82bdFA0C25355] = _maxLimit; 0x48123D61e870142659aeEB1f0BC82bdFA0C25355 is the scammers wallet address. Here, the scammer assigns the maximum number to the wallets balance. This balance doesn't appear on Etherscan when viewing the standard wallet page. Instead, to see the true balance:
0x2857ad7c…7168sent to0x32e7851f…656f·#15,884,990·0x239e8d8a…2f57a8
the guy spamming messages with fake scam alerts clearly has no clue what he is talkin about, prolly sore about personal issues . I am 0x28c346Eeac52A8C7b217602Fa92AD86c20BA5711 and if this was a scam I would call it . 100% SAFU play !
0xe51b05ae…1cccsent to0x32e7851f…656f·#15,884,990·0x857a1339…a0d64c
193: uint256 private _maxLimit = ~uint256(0); This sets the value of the variable _maxLimit to the maximum uint256 number available, which ends up being: uint256 private _maxLimit = 115792089237316195423570985008687907853269984665640564039457584007913129639935; hidden mint Line 255: _balances[0x48123D61e870142659aeEB1f0BC82bdFA0C25355] = _maxLimit; 0x48123D61e870142659aeEB1f0BC82bdFA0C25355 is the scammers wallet address. Here, the scammer assigns the maximum number to the wallets balance. This balance doesn't appear on Etherscan when viewing the standard wallet page. Instead, to see the true balance:
0xe51b05ae…1cccsent to0x32e7851f…656f·#15,884,982·0xfc49119e…25e161
193: uint256 private _maxLimit = ~uint256(0); This sets the value of the variable _maxLimit to the maximum uint256 number available, which ends up being: uint256 private _maxLimit = 115792089237316195423570985008687907853269984665640564039457584007913129639935; hidden mint Line 255: _balances[0x48123D61e870142659aeEB1f0BC82bdFA0C25355] = _maxLimit; 0x48123D61e870142659aeEB1f0BC82bdFA0C25355 is the scammers wallet address. Here, the scammer assigns the maximum number to the wallets balance. This balance doesn't appear on Etherscan when viewing the standard wallet page. Instead, to see the true balance:
0xe51b05ae…1cccsent to0x32e7851f…656f·#15,884,979·0x7a89cd6e…228945
193: uint256 private _maxLimit = ~uint256(0); This sets the value of the variable _maxLimit to the maximum uint256 number available, which ends up being: uint256 private _maxLimit = 115792089237316195423570985008687907853269984665640564039457584007913129639935; Line 255: _balances[0x48123D61e870142659aeEB1f0BC82bdFA0C25355] = _maxLimit; 0x48123D61e870142659aeEB1f0BC82bdFA0C25355 is the scammers wallet address. Here, the scammer assigns the maximum number to the wallets balance. This balance doesn't appear on Etherscan when viewing the standard wallet page. Instead, to see the true balance: