Token Overview
Name: Azure Delicacy
Symbol: AZCHEESE
Deployed On: 2025-01-06 11:34:41 UTC
Blockchain: BNB Chain
Contract Address: 0x578173e0094e2e51922f0d4686e4597ac2ed883f
Creator Address: 0xb0187414468244400cd62ba4b249403c0b71039e
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
Liquidity: 0
Market Cap: 0
Total Supply: 1,000,000,000
Circulating Supply: 1,000,000,000
Holders: 19 unique addresses
Token Audit Summary
Feature | Status | Description |
---|---|---|
Honeypot Status | False | Indicates if the token has mechanisms that could prevent selling. |
Contract Verification | True | 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 | False | 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 | True | 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 Azure Delicacy (AZCHEESE)?
To purchase Azure Delicacy, 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 Azure Delicacy (AZCHEESE)?
The current price of Azure Delicacy is approximately 0. For the most recent price, please check the chart link provided in the Token Overview section.
What is Azure Delicacy’s (AZCHEESE) contract address?
The smart contract address for Azure Delicacy is 0x578173e0094e2e51922f0d4686e4597ac2ed883f. Always verify the address on official sources before any transactions.
What is the market cap of Azure Delicacy (AZCHEESE)?
The market capitalization of Azure Delicacy is 0. This figure is calculated by multiplying the current token price by its circulating supply.
Liquidity and Trading Volume
How much liquidity is in the Azure Delicacy liquidity pool?
There is currently 0 in liquidity for Azure Delicacy. This amount can provide insights into the market’s depth and stability.
Technical Questions
Does Azure Delicacy (AZCHEESE) have a buy or sell tax?
Azure Delicacy has a buy tax of 0% and a sell tax of 0%. These taxes can affect transaction costs.
How many holders does Azure Delicacy (AZCHEESE) have?
As of now, Azure Delicacy is held by 19 unique addresses, indicating its distribution and adoption rate.
When was Azure Delicacy (AZCHEESE) launched?
Azure Delicacy was deployed on 2025-01-06 11:34:41 UTC, marking its introduction to the BNB Chain.
Security Checks
How can I perform a real-time honeypot check on Azure Delicacy?
To verify if Azure Delicacy is a honeypot, use the Real-Time Honeypot Check link provided at the top of the Token Overview section.
—————–