Need verifiable oracle data for your project?
DIA provides transparent, customizable price feeds across 50+ chains with fully auditable methodology.
Market cap
DeFiLlama estimate
DIA price
Total supply
Holders
126.6K VGBPpartial
DIA holds no verified contract address on Stellar, Ethereum. The figure above is a floor.
293holders
Measured on Base. Shares are of the Base supply, not the multi-chain total.
0 VGBPsince Sat, Aug 29 UTC
Change in the supply DIA reads across this coin’s chains, between two daily snapshots. Not mints minus redeems: DIA does not publish issuance flow.
Market data · CoinGecko
Market data · CoinGecko
Circulating supply · DeFiLlama
Aggregator figure, not a contract read. DIA’s own onchain supply is the separate series below.
Percentage change in VGBP's circulating supply as reported by DeFiLlama, measured against that source's own past. It is not a change in the onchain supply above, which DIA reads from the contracts directly and which is a different measurement of the same coin. A dash means the map has no reading close enough to the start of the window, a stretch inside it where supply was not reported at all, or a starting figure too small for a percentage to describe. Hover a dash for which.
2 of the 3 chains DIA holds a verified VGBP contract on carry a deployment date and are plotted here. The other 1 was verified without one and is left off the curve rather than dated to the day DIA read it.
DIA price
—
Peg deviation
—
Peg currency
GBP
Primary use
—
Last snapshot
Sat, Sep 5 UTC
0xaeb4bb7d…3a7bf411Explorer ↗0x7ae4265e…01f4bb7fExplorer ↗5H4voZhzyS…PW4YHWW1Explorer ↗Supply on this page is read from these contracts. Addresses are verified by DIA against the issuer’s own published documentation.
0xaeb4bb7d…3a7bf411freeze(address)paused()mint(address,uint256), configureMinter(address,uint256) +1eip1967-transparent0x7ae4265e…01f4bb7ffreeze(address)paused()mint(address,uint256), configureMinter(address,uint256) +1eip1967-transparent5H4voZhzyS…PW4YHWW1freezeAuthoritymintAuthorityRead from the deployed contract. “Not determined” means the contract’s full function set could not be enumerated, not that the capability is absent: a bytecode scan can confirm that a function exists and can never prove that one does not.