Compare KiloEx (KILO) vs Subsquid (SQD) Price & Performance
Price performance (Past 24H)
Key statistics
Key statistics
KiloEx vs Subsquid — how do they compare? KiloEx trades at Rp66.64 (market cap Rp14,15M, Rp2,63M 24h volume), while Subsquid trades at Rp796.26 (market cap Rp897,94M, Rp75,62M 24h volume). The key difference: Subsquid is far larger — about 63.5× KiloEx's market cap, and KiloEx's circulating supply is 211,7M / 1B KILO (22%) versus 1,1B / 1,3B SQD (84%) for Subsquid. Which is the better fit depends on your goals — on Pluang, investors hold KiloEx for 19 Days and Subsquid for 8 Days on average.
| KILO | SQD | |
|---|---|---|
Market Cap | Rp14,15M | Rp897,94M |
Volume (24h) | Rp2,63M | Rp75,62M |
Circulating Supply | 211,7M / 1B KILO (22%) | 1,1B / 1,3B SQD (84%) |
Typical Hold Time | 19 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
No sentiment data available yet.
About KiloEx
KiloEx is a next-generation decentralized exchange (DEX) created to offer a user-friendly experience for perpetual trading, fully integrated with Liquid Staking Token Finance (LSTfi). The platform combines advanced risk management, innovative trading features, and seamless multi-asset trading capabilities to transform decentralized trading. KiloEx emphasizes security, transparency, and accessibility, making it a dependable choice for both retail and institutional traders.
Read more on KILO →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 →
