Compare Parcl (PRCL) vs Subsquid (SQD) Price & Performance
Price performance (Past 24H)
Key statistics
Key statistics
Parcl vs Subsquid — how do they compare? Parcl trades at Rp90.68 (market cap Rp37,55M, Rp7,01M 24h volume), while Subsquid trades at Rp791.58 (market cap Rp887,08M, Rp73,46M 24h volume). The key difference: Subsquid is far larger — about 23.6× Parcl's market cap, and Parcl's circulating supply is 412,3M / 1B PRCL (42%) versus 1,1B / 1,3B SQD (84%) for Subsquid. Which is the better fit depends on your goals — on Pluang, investors hold Parcl for 16 Days and Subsquid for 8 Days on average.
| PRCL | SQD | |
|---|---|---|
Market Cap | Rp37,55M | Rp887,08M |
Volume (24h) | Rp7,01M | Rp73,46M |
Circulating Supply | 412,3M / 1B PRCL (42%) | 1,1B / 1,3B SQD (84%) |
Typical Hold Time | 16 Days | 8 Days |
Investor sentiment on Pluang
What Pluang investors did over the last 30 days
Investor sentiment on Pluang
What Pluang investors did over the last 30 days
About Parcl
The Parcl Ecosystem—comprising Parcl, Parcl Labs, and Parcl Limited—develops and governs the Parcl Protocol, a decentralized platform enabling users to take long or short positions on real-world real estate prices. By leveraging world-class real estate data from Parcl Labs, Parcl aims to create a liquid market around the largest asset class globally. The PRCL token powers the ecosystem, offering governance rights, access to Parcl Labs’ data and analytics, and network incentives.
Read more on PRCL →About Subsquid
Subsquid Network is a decentralized data lake and query engine designed to provide developers with fast, permissionless access to blockchain data. Its modular architecture, secured by zero-knowledge (ZK) proofs, enables scalable blockchain indexing, decentralized application (dApp) development, and robust analytics. Unlike rigid monolithic indexing frameworks that struggle to adapt in today's rapidly evolving blockchain environment, Subsquid offers a flexible, efficient, and decentralized alternative to centralized RPC and API providers. This approach paves the way for a more open, neutral, and developer-friendly Web3.
Read more on SQD →
