Name: Bitcoin Historical OnChain Data
Creator: Kaggle
License: https://www.apache.org/licenses/

About this Dataset

Bitcoin Historical OnChain Data

This dataset include some onchain indicator information at daily basis for Bitcoin. This informations:

exchange onchain market depth
inflow transaction count
inflow volume
netflows
open interest to market cap ratio
outflow transaction count
outflow volume
telegram sentiment
total flows
trades per side
twitter sentiment

Inflow Volume

IntoTheBlock has built a proprietary machine learning powered classifier to identify addresses of top centralized exchanges, including their deposit addresses, withdrawal addresses, hot wallets and cold wallets. With this classifier, IntoTheBlock can measure the total amount of a given crypto-asset flowing into exchanges and measures this in dollar and crypto terms. The result is the Inflow Volume indicator.

Outlow Volume

While Inflow Volume at times anticipate volatility, Outflow Volume is often more reactive. In other words, Outflow Volume often spikes following either a crash or a significant break-out as shown in the example above. This could potentially be interpreted as users going long and opting to hold their crypto outside centralized exchanges.

Total Flows
IntoTheBlock uses machine learning algorithms to identify centralized exchanges’ deposit and withdrawal addresses. Through this process, IntoTheBlock measures the total activity flowing in and out of centralized exchanges. The result is the Total Flows indicator which is measured the following way

Total Flows = Inflow Volume + Outlow Volume

Net Flows

The Net Flows indicator highlights trends of traders sending money in and out of exchanges. Recall that Net Flows are positive when more funds are entering than leaving exchanges. Therefore, we observe that positive Net Flows tend to coincide with periods following large increases in price (like LINK when it tripled between April and July) or confirmation of down-trends (as seen with LINK in late August).

Conversely, Net Flows are negative when a greater volume is being withdrawn from exchanges. This could be seen as a sign of accumulation (LINK in early August) or addresses buying back following large declines (LINK in early September).

While Net Flows also affect large cap crypto-assets, smaller cap tokens are more susceptible to large changes in prices deriving from exchange flows. This is simply a result of smaller caps requiring less capital in order to make market-moving trades. This is worth considering when using the Net Flows indicator to trade.

Net Flows = Inflow Volume - Outflow Volume

Outflow Transaction Count

The Outflow Transaction Count indicator provides indication of users withdrawing their funds from centralized exchanges likely to store in safer cold wallets. This is a valuable approximation of users going long and opting to hold their own funds. For this reason, outflows tend to spike as price crashes as pointed in the example above. While this can be the case on several occasions, natural fluctuations in exchanges’ flows can often have smaller spikes without regards to price action as well.

Inflow Transaction Count

As the name suggests, the Inflow Transaction Count indicator provides the number of incoming crypto transactions entering exchanges. While the Inflow Volume measures the aggregate dollar amount, which is influenced by whales’ transactions, the Inflow Transaction Count is a better approximation of the number of users sending funds into exchanges.

This indicator has also shown to rise along and anticipate periods of high volatility. For example, on September 1st, inflow transactions for Bitcoin hit a 3-month high preceding a decrease in price of 14% over the following 48 hours. While this pattern does tend to emerge, natural fluctuations in inflow transactions can also increase at times.

Tables

Itb Btc Exchange Onchain Market Depth Undefined 2023–0–1d0dc245

@kaggle.aski1140_intotheblock_bitcoin_onchain_data.itb_btc_exchange_onchain_market_depth_undefined_2023_0_1d0dc245

3.68 KB
14 rows
4 columns


CREATE TABLE itb_btc_exchange_onchain_market_depth_undefined_2023_0_1d0dc245 (
  "category" VARCHAR,
  "binance" DOUBLE,
  "bittrex" DOUBLE,
  "bitfinex" DOUBLE
);

Itb Btc Github Undefined 2023–06–19t16–48–45–495z

@kaggle.aski1140_intotheblock_bitcoin_onchain_data.itb_btc_github_undefined_2023_06_19t16_48_45_495z

26.63 KB
1140 rows
4 columns


CREATE TABLE itb_btc_github_undefined_2023_06_19t16_48_45_495z (
  "datetime" TIMESTAMP,
  "commits" BIGINT,
  "stars" BIGINT,
  "open_issues" BIGINT
);

Itb Btc Inflow Transaction Count Undefined 2023–06–19t F7fc61a3

@kaggle.aski1140_intotheblock_bitcoin_onchain_data.itb_btc_inflow_transaction_count_undefined_2023_06_19t_f7fc61a3

90.84 KB
4357 rows
3 columns


CREATE TABLE itb_btc_inflow_transaction_count_undefined_2023_06_19t_f7fc61a3 (
  "datetime" TIMESTAMP,
  "aggregated_exchanges" BIGINT,
  "price" DOUBLE
);

Itb Btc Inflow Volume Undefined 2023–06–19t16–45–51–762z

@kaggle.aski1140_intotheblock_bitcoin_onchain_data.itb_btc_inflow_volume_undefined_2023_06_19t16_45_51_762z

109.55 KB
4357 rows
3 columns


CREATE TABLE itb_btc_inflow_volume_undefined_2023_06_19t16_45_51_762z (
  "datetime" TIMESTAMP,
  "aggregated_exchanges" DOUBLE,
  "price" DOUBLE
);

Itb Btc Netflows Undefined 2023–06–19t16–46–26–728z

@kaggle.aski1140_intotheblock_bitcoin_onchain_data.itb_btc_netflows_undefined_2023_06_19t16_46_26_728z

108.78 KB
4357 rows
3 columns


CREATE TABLE itb_btc_netflows_undefined_2023_06_19t16_46_26_728z (
  "datetime" TIMESTAMP,
  "aggregated_exchanges" DOUBLE,
  "price" DOUBLE
);

Itb Btc Open Interest To Market Cap Ratio Undefined 20 A29a1484

@kaggle.aski1140_intotheblock_bitcoin_onchain_data.itb_btc_open_interest_to_market_cap_ratio_undefined_20_a29a1484

7.11 KB
176 rows
3 columns


CREATE TABLE itb_btc_open_interest_to_market_cap_ratio_undefined_20_a29a1484 (
  "datetime" TIMESTAMP,
  "ratio" DOUBLE,
  "price" DOUBLE
);

Itb Btc Outflow Transaction Count Undefined 2023–06–19–7e7eb69c

@kaggle.aski1140_intotheblock_bitcoin_onchain_data.itb_btc_outflow_transaction_count_undefined_2023_06_19_7e7eb69c

88.28 KB
4357 rows
3 columns


CREATE TABLE itb_btc_outflow_transaction_count_undefined_2023_06_19_7e7eb69c (
  "datetime" TIMESTAMP,
  "aggregated_exchanges" BIGINT,
  "price" DOUBLE
);

Itb Btc Outflow Volume Undefined 2023–06–19t16–46–17–119z

@kaggle.aski1140_intotheblock_bitcoin_onchain_data.itb_btc_outflow_volume_undefined_2023_06_19t16_46_17_119z

107.33 KB
4357 rows
3 columns


CREATE TABLE itb_btc_outflow_volume_undefined_2023_06_19t16_46_17_119z (
  "datetime" TIMESTAMP,
  "aggregated_exchanges" DOUBLE,
  "price" DOUBLE
);

Itb Btc Telegram Sentiment Undefined 2023–06–19t16–48–20–609z

@kaggle.aski1140_intotheblock_bitcoin_onchain_data.itb_btc_telegram_sentiment_undefined_2023_06_19t16_48_20_609z

39.65 KB
1431 rows
5 columns


CREATE TABLE itb_btc_telegram_sentiment_undefined_2023_06_19t16_48_20_609z (
  "datetime" TIMESTAMP,
  "positive" DOUBLE,
  "neutral" DOUBLE,
  "negative" DOUBLE,
  "price" DOUBLE
);

Itb Btc Total Flows Undefined 2023–06–19t16–46–32–829z

@kaggle.aski1140_intotheblock_bitcoin_onchain_data.itb_btc_total_flows_undefined_2023_06_19t16_46_32_829z

108.81 KB
4357 rows
3 columns


CREATE TABLE itb_btc_total_flows_undefined_2023_06_19t16_46_32_829z (
  "datetime" TIMESTAMP,
  "aggregated_exchanges" DOUBLE,
  "price" DOUBLE
);

Itb Btc Trades Per Side Undefined 2023–06–19t20–10–35–540z

@kaggle.aski1140_intotheblock_bitcoin_onchain_data.itb_btc_trades_per_side_undefined_2023_06_19t20_10_35_540z

31.04 KB
720 rows
7 columns


CREATE TABLE itb_btc_trades_per_side_undefined_2023_06_19t20_10_35_540z (
  "time_europe_istanbul" TIMESTAMP,
  "binance" DOUBLE,
  "binance_1" DOUBLE,
  "bittrex" DOUBLE,
  "bittrex_1" DOUBLE,
  "bitfinex" DOUBLE,
  "bitfinex_1" DOUBLE
);

Itb Btc Twitter Sentiment Undefined 2023–06–19t16–48–29–104z

@kaggle.aski1140_intotheblock_bitcoin_onchain_data.itb_btc_twitter_sentiment_undefined_2023_06_19t16_48_29_104z

48.69 KB
1431 rows
5 columns


CREATE TABLE itb_btc_twitter_sentiment_undefined_2023_06_19t16_48_29_104z (
  "datetime" TIMESTAMP,
  "positive" DOUBLE,
  "neutral" DOUBLE,
  "negative" DOUBLE,
  "price" DOUBLE
);