CryptoQuant User Guide
English
English
  • 🔍What is CryptoQuant
    • Introduction
      • How We Process Data
      • Why Trust CryptoQuant Metrics?
      • Why Market Driven?
    • Background Knowledge
      • What is On-Chain Data?
      • What are Entities?
      • What is a UTxO?
    • Our Product
  • 🎯QuickStart
    • 5 Minute Data Guide
      • 3 Key On-Chain Metrics
      • 3 Key Market Metrics
      • 3 Key Indicators
      • Deriving Insights
    • 5 Minute Feature Guide
      • 1. Charting Overview
      • 2. Set Alerts
      • 3. Dashboards
      • 4. Quicktake
      • 5. Top 15 Pro Charts
        • Miner Selling
        • Whale Accumulation
        • Large OTC deals
        • Buying/Selling Pressure
        • Market Trend
        • Market Sentiment
        • Whale Dumping
  • 📊CryptoQuant Metrics
    • Exchange Flows/Indicators
      • Exchange In/Outflow and Netflow
      • Exchange Reserve
      • Exchange to Exchange
      • Exchange Addresses Count
      • Exchange Transactions Count
      • Fund Flow Ratio
      • Exchange Supply Ratio
      • Exchange Inflow CDD
      • Exchange Inflow - Spent Output Age Bands
      • Exchange Inflow - Spent Output Value Bands
    • Miner Flows/Indicators
      • Miner Outflow
      • Miner to Exchange
      • Miners' Position Index (MPI)
      • Miner Supply Ratio
    • UTxO Data/Indicators
      • Profit and Loss (UTxO)
      • Profit and Loss (Supply)
      • Coin Days Destroyed (CDD)
      • Binary CDD
      • Mean Coin Age (MCA)
      • Sum Coin Age (SCA)
      • Sum Coin Age Distribution (SCA Distribution)
      • Spent Output Profit Ratio (SOPR)
        • aSOPR (Adjusted SOPR)
        • STH-SOPR
        • LTH-SOPR
        • SOPR Ratio (LTH-SOPR/STH-SOPR)
      • Net Unrealized Profit/Loss (NUPL)
      • UTXO Bands (Age)
        • UTXO Age Bands
        • Realized Cap - UTXO Age Bands
        • Realized Price - UTXO Age Bands
        • UTXO Count - Age Bands
        • Spent Output Age Bands
      • UTXO Bands (Value)
        • UTXO Value Bands
        • Realized Cap - UTXO Value Bands USD
        • UTXO Count - Value Bands
        • Spent Output Value Bands
    • Market Data/Indicators
      • Open Interest
      • Funding Rates
      • Estimated Leverage Ratio
      • Taker Buy Sell Volume/Ratio
      • Capitalization models
      • Realized Price
      • Exchange Whale Ratio
      • MVRV (Market Value to Realized Value) Ratio
    • Network Indicators
      • NVT Ratio
      • NVT Golden Cross
      • Puell Multiple
      • Stock to Flow Ratio
      • Stock to Flow Reversion
      • NVM Ratio
    • Stablecoin Exchange Flows/Indicators
      • Stablecoin Network Data
      • Stablecoin Exchange In/Outflow & Netflow
      • Stablecoin Exchange Reserve
      • Stablecoin Exchange Addresses Count
      • Stablecoin Exchange Transactions Count
      • Stablecoins Ratio
      • Stablecoin Supply Ratio (SSR)
    • Fund Data & Premium
      • Grayscale Bitcoin Trust (GBTC)
        • GBTC Digital Asset Holdings
        • GBTC Premium or Discount
      • Grayscale Ethereum Trust (ETHE)
        • ETHE Digital Asset Holdings
        • ETHE Premium or Discount
      • Coinbase Premium
      • Korea Premium Index
      • Bank Supply Ratio
  • 🛠️Web3 Analytics Tool
    • Overview
    • Cohort Data Navigation
    • Query Data Navigation
    • How to Use(Query Tool)
      • 1. DateTime Aggregation
      • 2. Query Block - Metric
      • 3. Query Block - Where
      • 4. Query Block - Group by
      • 5. Query Block - Join
      • 6. Query Block - Order by
      • 7. Save and Run
      • 8. Editing the Result
      • 9. Visualization
        • Table
        • Pie
        • Serial
        • Number
        • Pivot Table
  • 📌Reference
    • FAQ
    • Community Guidelines
    • Community Links
Powered by GitBook
On this page
  • Join
  • How to use

Was this helpful?

  1. Web3 Analytics Tool
  2. How to Use(Query Tool)

5. Query Block - Join

Previous4. Query Block - Group byNext6. Query Block - Order by

Last updated 1 year ago

Was this helpful?

Join

Join is used when you want to merge two tables within one Query Block. For example, you may want to use the Ethereum transaction table and the address label information from metadata. Using join, you can match the from or to address of the Ethereum transaction with the label to merge the tables.

How to use

  1. To activate the join input window, click on the +Join button at the top of the Query Block.

  2. Select the new table you want to join in the table selection window.

  3. You can change the Join option between the two tables. There are four Join options available: Inner, Left Outer, Right Outer, and Full Outer. The default option is Inner Join.

    1. Inner Join: Inner Join returns only the matching rows from both tables based on the join condition specified. The result set only includes the rows that have matching values in both tables.

    2. Left Outer Join: A Left Outer Join returns all the rows from the left table (the first table in the join clause), and the matching rows from the right table (the second table in the join clause). If there is no match, NULL values will be displayed for the right table's columns.

    3. Right Outer Join: The Right Outer Join is similar to the Left Outer Join, but returns all the rows from the right table and the matching rows from the left table. If there is no match, NULL values will be displayed for the left table's columns.

    4. Full Outer Join: A Full Outer Join returns all the rows from both tables, with matching rows combined, and non-matching rows from either table displayed as NULL values. If there is no match in either table, NULL values will be displayed for all columns from the non-matching table.

  4. By default, the first table selected is referred to as t1, and the newly added table for joining as t2. The name of the tables can be customized.

  5. After selecting the table to join, the on condition needs to be selected at the bottom. The on condition determines which column to base the joining of the two tables on. For example, the "to address" of the transaction and the "address" of the label table can be matched. In this case, the "to_address" column from t1 and the "address" column from t2 are selected. If the data in the selected on columns is the same, the information from the two tables is considered connected and merged.

  6. After joining, columns from both tables can be used in Metric, Where, and Group by sections below.

🛠️