Skip to content
Shivacha — Simplifying Tech Solutions
Shivacha Web3Blockchain Data & On-Chain Analytics

On-Chain Analytics

On-chain analytics platforms — protocol metrics, user behaviour, token flows and custom dashboards.

Contract events · EVM network
Illustrative
  1. Wallet
  2. Smart contract
  3. Blockchain
  4. Indexer
  5. API
  6. Application

#…4812

12 conf.

#…4813

11 conf.

#…4814

10 conf.

#…4815

pending

Decoded events

  • Deposit(0x8f2…a91, 500)confirmed
  • Transfer(0x1c7…4de → 0x9b0…77f)confirmed
  • RoleGranted(PAUSER, multisig)timelock

RPC failover · 3 providers · reorg-safe indexing

Overview

On-chain analytics answers questions about protocols, tokens and users: who uses a protocol, how value flows, which cohorts retain, where liquidity moves. We build analytics platforms with indexed data, metric definitions, cohort analysis and dashboards for protocol teams, investors and ecosystem funds.

Common use cases

  • Protocol growth analyticsUsage, retention and revenue.
  • Token flow analysisHolder distribution and movements.
  • Ecosystem dashboardsMetrics across an ecosystem.
  • Investor analyticsDue diligence data.

Quick answers

On-Chain Analytics at a glance

The essentials in brief. Every project is scoped individually — ask us for specifics.

What is on-chain analytics?
On-chain analytics platforms — protocol metrics, user behaviour, token flows and custom dashboards.
Who is it for?
Typically Web3 startups, fintechs adding digital assets, and institutions exploring tokenization, stablecoins or on-chain settlement.
What does Shivacha provide?
  • Metric definitions
  • Cohort analysis
  • Flow analysis
  • Dashboards
  • Custom queries
  • Alerts
Which technologies are used?
The Graph, ClickHouse, PostgreSQL, Apache Kafka, Go (Golang), Rust — chosen to fit your stack and constraints.
How does the process work?
Data requirements → Indexing design → Pipeline build → Serving layer → Operations.
What affects the cost?
  • Contract complexity and number of chains
  • Custody and wallet model
  • Independent audit scope
  • Indexing, analytics and back-office tooling
  • Compliance integrations (KYC, AML, Travel Rule)
  • Upgradeability and governance requirements
How long does it take?
A focused contract system or dApp MVP typically takes 8–14 weeks plus independent audit time; institutional platforms usually take 4–9 months.
How do I get started?
Share a short brief in the form below, book a 30-minute call or message us on WhatsApp. A senior engineer replies within one business day; NDA on request.

Capabilities

What we deliver

Metric definitions

Consistent, documented metrics.

Cohort analysis

User retention and behaviour.

Flow analysis

Value movement across addresses.

Dashboards

Interactive exploration.

Custom queries

Analyst access to data.

Alerts

Significant activity notifications.

Architecture

Engineered right from day one

The layers we typically design for blockchain data & on-chain analytics, adapted to your stack and partners.

  • Reorg safetyConfirmed vs pending data handled explicitly.
  • Completeness checksAutomated checks that no blocks or events were missed.
  • Query performanceColumnar storage for analytics, relational for applications.
  • CostNode and RPC costs managed with caching and archive strategies.
Blockchain Data & On-Chain Analytics · reference architecture
5Sources
Full & archive nodesRPC providersEvent logsTraces
4Ingestion
Block streamingReorg handlingDecoding
3Processing
NormalisationEnrichmentPricingLabels
2Storage
PostgreSQLClickHouseData warehouse
1Access
APIs & GraphQLDashboardsAlertsExports

Delivery

How an engagement runs

  1. 1

    Data requirements

    Chains, contracts, entities, freshness and query patterns.

  2. 2

    Indexing design

    Subgraphs, custom indexers or hybrid, with reorg strategy.

  3. 3

    Pipeline build

    Ingestion, decoding, enrichment and storage.

  4. 4

    Serving layer

    APIs, dashboards and alerts for consumers.

  5. 5

    Operations

    Monitoring of lag, completeness and data quality.

Security

Security built into delivery

Controls we apply by default on this kind of work — not a separate phase at the end.

Specification first

Roles, invariants and threat model documented before code.

Adversarial testing

Fuzz, invariant and fork tests plus static analysis on every change.

Key management

Admin keys in multisig or MPC with timelocks on sensitive actions.

Independent audit

Code prepared for — and we recommend — an external audit before mainnet value.

Dedicated team

Data Engineering Team

Engineers for pipelines, warehouses, streaming and blockchain data.

FAQ

Frequently asked questions

How do you identify users from addresses?

Addresses are pseudonymous; heuristics and labels group them, but true identity is not inferred.

Can dashboards be public?

Yes, public or private dashboards are both supported.

Should we use The Graph or a custom indexer?

Subgraphs are fast to build for contract-event data on supported networks. Custom indexers suit high volume, multi-chain, trace-level or complex enrichment needs. Many platforms use both.

Can you reconcile on-chain data with our internal ledger?

Yes. Reconciling on-chain activity with internal and custodian records is a core part of our digital asset and fintech work.

Next step

Discuss Your Blockchain Project.

Tell us about your on-chain analytics requirements — goals, timeline and constraints. We will reply with questions, an approach and next steps.

  • Senior engineer reads every enquiry
  • Reply within one business day
  • NDA on request

Prefer to talk first?

Book a 30-minute call, or message the nearest team on WhatsApp.

Book a Call

Your details are used only to reply to this enquiry.

Step 1 of 2Your details

Confidential. We reply within one business day. Privacy