Market Cap
—
Total Issuance
— PDEX
In Stake
— PDEX
AVG APY
—
Recent Blocks
View allRecent Transactions
View allNetwork Information
Active Validators
Loading...Staking Rewards
Enter a Polkadex wallet address to view its claimed staking reward history, then download it as CSV or JSON.
Council
Members
| Account | Backing Stake |
|---|---|
| Fetching council members... | |
Runners Up
| Account | Backing Stake |
|---|---|
| Fetching runners up... | |
Candidates
| Account | Backing Stake |
|---|---|
| Fetching candidates... | |
Submit Candidacy
Submit your candidacy for the Polkadex Council. This action requires a connected wallet extension.
Vote for Council
Vote for up to 16 candidates. Separate multiple Polkadex addresses with commas.
Vote on Referendum
Lock PDEX behind your vote — higher conviction multiplies your vote weight but extends the lock period after enactment.
VoteLockingPeriod. Lock starts only after the referendum passes; failed votes don't extend any lock.Submit Treasury Proposal
Request a spend from the on-chain Treasury. A bond is reserved from your account until the proposal is approved or rejected.
Stake & Nominate
Add to your bond and pick the validators you want to back. Your nomination set is replaced with whatever appears in the “Selected” box on submit.
Send PDEX
Transfer PDEX from the connected wallet to any Polkadex address. The transaction is signed and submitted by your wallet extension.
On-chain identity
Register a display name and contact handles for this address. The data is stored on chain so other Polkadex apps see it too — not just this explorer. A small refundable deposit is locked while the identity exists.
Each field is limited to 32 bytes by the runtime. Leave any field blank to omit it; you must fill at least one.
Top Token Holders
Loading...Transactions History
Loading...Blocks History
Loading...Polkadex Events (excl transactions)
Loading...Privacy Policy
Last updated: June 2026Short version. The Polkadex Explorer is a read-only window onto a public blockchain. We don't run analytics, we don't set tracking cookies, we don't sell or share data with third parties. We store a handful of small items in your browser's local storage to remember your preferences, and our server logs the kind of request data a normal web server logs.
1. Who we are
The Polkadex Explorer (explorer.polkadex.ee) is operated by the Polkadex Foundation. This policy covers the explorer specifically; the Foundation's wider organisational privacy policy is available at the Polkadex Privacy Policy.
2. What we store about you
The explorer stores three kinds of data:
a) On-chain data. All blocks, extrinsics, events, balances, validators, governance proposals, and votes you see on this site are already public on the Polkadex Mainnet. We index them so you can browse them efficiently. Anyone with a Polkadex node has access to the same data. We cannot delete on-chain data — that's a property of the blockchain itself, not of this explorer.
b) Local storage on your device. We keep a small set of keys in your browser's localStorage so the explorer remembers your choices between visits. See the Cookie & Storage Notice for the full list. This data never leaves your device unless you explicitly sign a transaction or post a community label.
c) Server logs. Our backend logs the standard request data a web server records: source IP (often a Cloudflare IP, since we're behind Cloudflare), user-agent, requested URL, response code, and timestamp. We use these to debug errors and measure traffic shape. Logs are retained for 30 days and then rotated out.
3. Wallet addresses and signatures
If you connect a wallet, the explorer reads your account's public address from your wallet extension. Public addresses are not personal data on their own under most privacy frameworks — they are pseudonymous identifiers anyone can derive from a public key — but they can become personal if linked to your identity, which is something you control. We never request your private key, mnemonic, or secret seed phrase. Any wallet extension that asks the explorer for these is malicious.
When you post a community label, a discussion message, or a vote, your wallet signs the action with your private key. The signed payload — including your address and the signature — is stored on our server (for labels and discussions) or broadcast to the chain (for votes). You can ask us to remove labels, votes, or discussion messages you authored; contact us via the channels listed below.
4. Third-party services
The explorer integrates with:
— Cloudflare as a CDN and DDoS shield. Cloudflare sees your IP. Their privacy policy is at cloudflare.com/privacypolicy.
— Browser wallet extensions (Polkadot.js, Talisman, SubWallet, Nova Wallet) when you click Connect Wallet. The explorer doesn't share any data with them; they expose your account list to us with your explicit permission.
— A PDEX price feed (CoinGecko/Coinpaprika public API) that runs server-side. Your browser does not contact these endpoints directly.
— A transactional email provider (Postmark by default; SendGrid as an alternative) that delivers your governance email alerts if and only if you opt in via the "Get email alerts" button. They see your email address and the alert content to send the message; they don't get your IP, your wallet, or anything else from us. We don't share your address with them for any purpose besides delivery.
We do not load Google Analytics, Mixpanel, Segment, advertising pixels, or any other analytics/tracking script. The explorer's JavaScript bundle is self-hosted; there are no third-party scripts loaded from external CDNs that could fingerprint you.
5. Email alerts (optional)
If you opt in to email alerts via the "Get email alerts" button, we store your email address, a randomly-generated confirmation token, an independent randomly-generated unsubscribe token, your selected event preferences, and timestamps. We use the email solely to deliver the alerts you subscribed to. There is no marketing.
Subscriptions use double opt-in: we email a confirmation link first, and only confirmed subscribers ever receive alerts. Every alert email contains a one-click unsubscribe link that works without login. Unsubscribing immediately stops all future alerts. We retain your subscription row marked as unsubscribed (rather than deleting) so accidental re-signups can be re-confirmed by you — request full deletion via the contact channels below and we'll wipe the row.
6. Your rights (GDPR / UK GDPR / CCPA)
You have the right to (a) know what personal data we hold about you, (b) request a copy, (c) request correction or deletion, and (d) object to processing. For the explorer specifically:
— Local storage: clear it any time via your browser settings, or click "Reset preferences" on the Cookies page.
— Community labels, votes, discussion messages: message us with the wallet that signed them (we'll verify via a fresh signature) and we'll delete them.
— Server access logs: we don't have a way to identify you within them unless you tell us your IP and time-window, but if you do, we'll delete matching entries on request.
— On-chain data: we cannot delete this. It's on the blockchain, not on our server.
7. Children
The explorer isn't directed at children under 16. We don't knowingly process data from anyone under 16. If you believe a child has used the explorer in a way that needs attention, contact us.
8. Changes to this policy
We'll update the "Last updated" date at the top of this page when this policy changes. Material changes will also be announced on our community channels.
8. Contact
Open an issue at github.com/Polkadex-Substrate or reach the team via the official channels listed at polkadex.ee.
Cookie & Storage Notice
Last updated: June 2026The Polkadex Explorer does not set tracking cookies. We use your browser's localStorage to remember your preferences between visits. Local storage stays on your device and is never sent over the network to us — unlike cookies, which are sent with every request.
What we store
Every key the explorer writes is prefixed with pdex_ for easy identification. Here's the full list:
| Key | What it stores | Why |
|---|---|---|
pdex_wallet | Connected wallet address and source extension name. | So the My Account page works without re-connecting on every reload. |
pdex_last_used_address | The most recently active address when your wallet has multiple accounts. | So we can default to the right account instead of always picking the first one. |
pdex_watchlist_v1 | Addresses, validators, and governance items you've starred. | So your watchlist follows you across sessions. |
pdex_labels_session | Short-lived signed bearer token (about 24 hours) for posting/voting on community labels. | So you don't have to re-sign every time you vote on a label. |
pdex_tour_seen_v1 | A boolean flag once you've completed the onboarding tour. | So we don't pop the tour up again every visit. |
pdex_banner_dismissed | A flag set when you dismiss the storage notice banner. | So we don't show it again. |
pdex_apr_period | The APR-history window you last picked (7d / 30d / 90d / 6m / 1y / all-time). | So your selection persists on the My Account page. |
pdex_price_period | The time window you last picked on the full-screen /price chart (7 / 30 / 90 / 365 / 4000 days). | So your selection persists between visits. |
pdex_home_snapshot | A small JSON cache of the home-page stat values (price, market cap, total issuance, in-stake, AVG APY, era, validators, nominators, max active stake) plus a save timestamp. | So returning visitors see populated home-page cells instantly while live data loads in the background. Expires after 7 days. |
pdex_wallet_dashboard:<address> | One JSON snapshot of the My Account dashboard payload (balance, staking positions, recent activity, price history, reward history) per address you've viewed, plus a save timestamp. | So returning to the dashboard renders instantly while the live data refreshes in the background. Expires after 30 minutes. |
pdex_gov_seen_ref | The highest democracy referendum index you've been notified of. | So new-event banners and toasts only pop for referenda tabled after the last one you saw. |
pdex_gov_seen_proposal | The highest public-proposal index you've been notified of. | Same as above for democracy public proposals. |
pdex_gov_banner_dismissed_ref | Index of the most recent referendum banner you closed. | So a banner you dismissed stays dismissed for that specific event; a newer event still triggers a fresh one. |
pdex_gov_banner_dismissed_proposal | Index of the most recent proposal banner you closed. | Same as above for public proposals. |
| Email alerts (if you opted in) are NOT stored in your browser. Your email address and preferences live on our server only. See the privacy policy section 5 for details. | ||
What we do NOT store
We do not set any tracking cookies. We do not load Google Analytics, Mixpanel, Segment, advertising pixels, or any other third-party analytics or tracking script. There are no third-party scripts in the explorer's HTML — every script you see runs from explorer.polkadex.ee.
Sessions
We use sessionStorage (cleared when you close the tab) for one transient flag: pdex_skip_wallet_auto_pick — set when you click "Switch wallet" so we don't immediately re-pick the same account.
Reset everything
You can clear every pdex_* key in your browser at any time. The button below removes them all and reloads the page.
Equivalent to clearing site data in your browser's developer tools.
Read more
See our Privacy Policy for the full picture, including server logs, third-party services we integrate with, and how to exercise your data-subject rights.