Token Overview
Name: Pepe On Fire
Symbol: PFIRE
Deployed On: 2024-07-22 21:29:46 UTC
Blockchain: BNB Chain
Contract Address: 0x4e4f698215e04f69e3ded76ac638988b6014f1ee
Creator Address: 0xaf45055c6d23d9d187044aedea08589af505a4d6
View Token Chart – Explore the token’s trading chart and transactions.
Real-Time Honeypot Check – Verify if the token is a honeypot.
Financials & Supply Information
Price: 0.368570051286325926
Liquidity: 605218
Market Cap: 368,570
Total Supply: 1,000,000
Circulating Supply: 1,000,000
Holders: 7 unique addresses
Token Audit Summary
Feature | Status | Description |
---|---|---|
Honeypot Status | False | Indicates if the token has mechanisms that could prevent selling. |
Contract Verification | False | Shows whether the token’s contract is verified for transparency. |
Buy Tax | 0 | The tax rate applied to buying transactions. |
Sell Tax | 0 | The tax rate applied to selling transactions. |
Ownership Renounced | True | Whether the original creators have given up control over the contract. |
Proxy Enabled | False | If the contract can be upgraded or changed via a proxy contract. |
Mintable | False | Indicates if new tokens can be created post-launch. |
Destructable | False | Whether the contract can be destroyed, removing it from the blockchain. |
External Calls | True | If the contract interacts with other contracts or addresses. |
Hidden Ownership | False | Shows if the owner’s identity is obscured within the contract. |
Pausable | False | Whether the contract allows pausing the token transfers. |
Cooldown Mechanism | False | Indicates a mandatory wait time between transactions. |
Transaction Limit | False | If there’s a cap on the amount or number of transactions in a given timeframe. |
Balances Modifiable | False | Whether the token balances can be altered externally. |
Ownership Modifiable | False | If the contract ownership can be transferred or changed. |
Tax Modifiable | False | Indicates if the transaction tax rate can be adjusted. |
Wallet Tax | False | Shows if specific wallets are taxed differently from standard transactions. |
Blacklist Functionality | False | Whether the contract can blacklist addresses, preventing their participation. |
Whitelist Exemptions | False | If certain addresses are exempt from restrictions or taxes applied to general users. |
Frequently Asked Questions
Buying and Selling Tokens
How do I buy Pepe On Fire (PFIRE)?
To purchase Pepe On Fire, use decentralized exchanges (DEXs) like PancakeSwap or 1inch. For direct links and the best routes, refer to the ‘View Token Chart’ section on our site.
Token Information
What is the current price of Pepe On Fire (PFIRE)?
The current price of Pepe On Fire is approximately 0.368570051286325926. For the most recent price, please check the chart link provided in the Token Overview section.
What is Pepe On Fire’s (PFIRE) contract address?
The smart contract address for Pepe On Fire is 0x4e4f698215e04f69e3ded76ac638988b6014f1ee. Always verify the address on official sources before any transactions.
What is the market cap of Pepe On Fire (PFIRE)?
The market capitalization of Pepe On Fire is 368,570. This figure is calculated by multiplying the current token price by its circulating supply.
Liquidity and Trading Volume
How much liquidity is in the Pepe On Fire liquidity pool?
There is currently 605218 in liquidity for Pepe On Fire. This amount can provide insights into the market’s depth and stability.
Technical Questions
Does Pepe On Fire (PFIRE) have a buy or sell tax?
Pepe On Fire has a buy tax of 0% and a sell tax of 0%. These taxes can affect transaction costs.
How many holders does Pepe On Fire (PFIRE) have?
As of now, Pepe On Fire is held by 7 unique addresses, indicating its distribution and adoption rate.
When was Pepe On Fire (PFIRE) launched?
Pepe On Fire was deployed on 2024-07-22 21:29:46 UTC, marking its introduction to the BNB Chain.
Security Checks
How can I perform a real-time honeypot check on Pepe On Fire?
To verify if Pepe On Fire is a honeypot, use the Real-Time Honeypot Check link provided at the top of the Token Overview section.
—————–