timestamp stringdate 2026-01-01 00:00:00 2026-01-30 23:00:00 | return_pct float64 -1.13 1.35 | abs_move float64 0 1.35 | hour int64 0 23 |
|---|---|---|---|
2026-01-01 00:00:00 | 0.17385 | 0.17385 | 0 |
2026-01-01 01:00:00 | -0.048393 | 0.048393 | 1 |
2026-01-01 02:00:00 | 0.226691 | 0.226691 | 2 |
2026-01-01 03:00:00 | 0.53306 | 0.53306 | 3 |
2026-01-01 04:00:00 | -0.081954 | 0.081954 | 4 |
2026-01-01 05:00:00 | -0.081948 | 0.081948 | 5 |
2026-01-01 06:00:00 | 0.552724 | 0.552724 | 6 |
2026-01-01 07:00:00 | 0.268602 | 0.268602 | 7 |
2026-01-01 08:00:00 | -0.164316 | 0.164316 | 8 |
2026-01-01 09:00:00 | 0.189896 | 0.189896 | 9 |
2026-01-01 10:00:00 | -0.162196 | 0.162196 | 10 |
2026-01-01 11:00:00 | -0.163005 | 0.163005 | 11 |
2026-01-01 12:00:00 | 0.084687 | 0.084687 | 12 |
2026-01-01 13:00:00 | -0.669648 | 0.669648 | 13 |
2026-01-01 14:00:00 | -0.603721 | 0.603721 | 14 |
2026-01-01 15:00:00 | -0.196801 | 0.196801 | 15 |
2026-01-01 16:00:00 | -0.354491 | 0.354491 | 16 |
2026-01-01 17:00:00 | 0.109987 | 0.109987 | 17 |
2026-01-01 18:00:00 | -0.317808 | 0.317808 | 18 |
2026-01-01 19:00:00 | -0.494306 | 0.494306 | 19 |
2026-01-01 20:00:00 | 0.512977 | 0.512977 | 20 |
2026-01-01 21:00:00 | -0.079022 | 0.079022 | 21 |
2026-01-01 22:00:00 | 0.023635 | 0.023635 | 22 |
2026-01-01 23:00:00 | -0.498662 | 0.498662 | 23 |
2026-01-02 00:00:00 | -0.190534 | 0.190534 | 0 |
2026-01-02 01:00:00 | 0.038823 | 0.038823 | 1 |
2026-01-02 02:00:00 | -0.402848 | 0.402848 | 2 |
2026-01-02 03:00:00 | 0.131494 | 0.131494 | 3 |
2026-01-02 04:00:00 | -0.210224 | 0.210224 | 4 |
2026-01-02 05:00:00 | -0.102093 | 0.102093 | 5 |
2026-01-02 06:00:00 | -0.210597 | 0.210597 | 6 |
2026-01-02 07:00:00 | 0.648297 | 0.648297 | 7 |
2026-01-02 08:00:00 | -0.004724 | 0.004724 | 8 |
2026-01-02 09:00:00 | -0.370199 | 0.370199 | 9 |
2026-01-02 10:00:00 | 0.287891 | 0.287891 | 10 |
2026-01-02 11:00:00 | -0.427295 | 0.427295 | 11 |
2026-01-02 12:00:00 | 0.073102 | 0.073102 | 12 |
2026-01-02 13:00:00 | -0.685885 | 0.685885 | 13 |
2026-01-02 14:00:00 | -0.464865 | 0.464865 | 14 |
2026-01-02 15:00:00 | 0.068901 | 0.068901 | 15 |
2026-01-02 16:00:00 | 0.258463 | 0.258463 | 16 |
2026-01-02 17:00:00 | 0.059979 | 0.059979 | 17 |
2026-01-02 18:00:00 | -0.040477 | 0.040477 | 18 |
2026-01-02 19:00:00 | -0.105386 | 0.105386 | 19 |
2026-01-02 20:00:00 | -0.517483 | 0.517483 | 20 |
2026-01-02 21:00:00 | -0.251945 | 0.251945 | 21 |
2026-01-02 22:00:00 | -0.161224 | 0.161224 | 22 |
2026-01-02 23:00:00 | 0.369993 | 0.369993 | 23 |
2026-01-03 00:00:00 | 0.120266 | 0.120266 | 0 |
2026-01-03 01:00:00 | -0.617064 | 0.617064 | 1 |
2026-01-03 02:00:00 | 0.113429 | 0.113429 | 2 |
2026-01-03 03:00:00 | -0.134779 | 0.134779 | 3 |
2026-01-03 04:00:00 | -0.236923 | 0.236923 | 4 |
2026-01-03 05:00:00 | 0.214087 | 0.214087 | 5 |
2026-01-03 06:00:00 | 0.36085 | 0.36085 | 6 |
2026-01-03 07:00:00 | 0.325948 | 0.325948 | 7 |
2026-01-03 08:00:00 | -0.293726 | 0.293726 | 8 |
2026-01-03 09:00:00 | -0.108224 | 0.108224 | 9 |
2026-01-03 10:00:00 | 0.115942 | 0.115942 | 10 |
2026-01-03 11:00:00 | 0.341441 | 0.341441 | 11 |
2026-01-03 12:00:00 | -0.167711 | 0.167711 | 12 |
2026-01-03 13:00:00 | -0.064981 | 0.064981 | 13 |
2026-01-03 14:00:00 | -0.387217 | 0.387217 | 14 |
2026-01-03 15:00:00 | -0.418672 | 0.418672 | 15 |
2026-01-03 16:00:00 | 0.284384 | 0.284384 | 16 |
2026-01-03 17:00:00 | 0.474684 | 0.474684 | 17 |
2026-01-03 18:00:00 | -0.025204 | 0.025204 | 18 |
2026-01-03 19:00:00 | 0.351237 | 0.351237 | 19 |
2026-01-03 20:00:00 | 0.126573 | 0.126573 | 20 |
2026-01-03 21:00:00 | -0.225792 | 0.225792 | 21 |
2026-01-03 22:00:00 | 0.126488 | 0.126488 | 22 |
2026-01-03 23:00:00 | 0.538313 | 0.538313 | 23 |
2026-01-04 00:00:00 | -0.012539 | 0.012539 | 0 |
2026-01-04 01:00:00 | 0.547625 | 0.547625 | 1 |
2026-01-04 02:00:00 | -0.916911 | 0.916911 | 2 |
2026-01-04 03:00:00 | 0.287666 | 0.287666 | 3 |
2026-01-04 04:00:00 | 0.030466 | 0.030466 | 4 |
2026-01-04 05:00:00 | -0.104653 | 0.104653 | 5 |
2026-01-04 06:00:00 | 0.032116 | 0.032116 | 6 |
2026-01-04 07:00:00 | -0.695649 | 0.695649 | 7 |
2026-01-04 08:00:00 | -0.076885 | 0.076885 | 8 |
2026-01-04 09:00:00 | 0.124989 | 0.124989 | 9 |
2026-01-04 10:00:00 | 0.517263 | 0.517263 | 10 |
2026-01-04 11:00:00 | -0.181395 | 0.181395 | 11 |
2026-01-04 12:00:00 | -0.282973 | 0.282973 | 12 |
2026-01-04 13:00:00 | -0.175615 | 0.175615 | 13 |
2026-01-04 14:00:00 | 0.320391 | 0.320391 | 14 |
2026-01-04 15:00:00 | 0.115063 | 0.115063 | 15 |
2026-01-04 16:00:00 | -0.185416 | 0.185416 | 16 |
2026-01-04 17:00:00 | 0.179644 | 0.179644 | 17 |
2026-01-04 18:00:00 | 0.033977 | 0.033977 | 18 |
2026-01-04 19:00:00 | 0.339026 | 0.339026 | 19 |
2026-01-04 20:00:00 | -0.245719 | 0.245719 | 20 |
2026-01-04 21:00:00 | -0.114682 | 0.114682 | 21 |
2026-01-04 22:00:00 | -0.137238 | 0.137238 | 22 |
2026-01-04 23:00:00 | -0.51223 | 0.51223 | 23 |
2026-01-05 00:00:00 | 0.103642 | 0.103642 | 0 |
2026-01-05 01:00:00 | 0.091369 | 0.091369 | 1 |
2026-01-05 02:00:00 | 0.00179 | 0.00179 | 2 |
2026-01-05 03:00:00 | -0.082105 | 0.082105 | 3 |
How Volatile Is a 24/7 Market? A Simple Data Experiment
Traditional financial markets have a familiar rhythm. They open, trade for several hours, and eventually close. Digital asset markets work differently: activity continues around the clock, across countries, time zones, and weekends.
This dataset project explores a simple question: does a market that never closes behave the same way throughout all 24 hours?
At first, “24/7 trading” can make every hour sound interchangeable. In practice, availability and activity are two different things. Participation changes throughout the day, liquidity can shift, and market activity may rise or fall as different regions become active.
The purpose of this project is not to predict prices or identify the “best” trading hour. Instead, it demonstrates a simple way to organize hourly observations and examine volatility using Python.
What Do We Mean by Volatility?
Volatility sounds more complicated than it needs to be. At a basic level, it describes how much prices move over a given period.
Imagine that a market rises 0.8% during one hour and falls 0.8% during another. The direction is different, but the size of the movement is identical.
For this experiment, I use absolute percentage movement as a simple measure. A return of +0.8% and a return of -0.8% are therefore both treated as a movement of 0.8%.
This lets us ignore direction for a moment and focus on a different question: how large are the movements occurring during each hour of the day?
Data Structure
Market information is commonly organized into candlestick data containing open, high, low and close prices for a particular interval.
While looking into how this information is structured programmatically, I reviewed the BYDFi API documentation as a reference for market endpoints and candlestick data.
For this project, however, I decided to work with simulated hourly observations rather than data pulled directly from a live API. This keeps the experiment simple and reproducible without requiring API credentials or depending on a live service.
The trade-off is important: simulated data cannot tell us how a real asset actually behaves. The dataset demonstrates an analytical workflow rather than documenting a real trading pattern.
Dataset Design
The example dataset represents 30 days of hourly observations, giving us 720 timestamps in total.
Each observation can be organized around three simple fields:
- timestamp: the date and hour of the observation
- return_pct: the simulated percentage movement during that hour
- abs_move: the absolute size of that percentage movement
We can also extract the hour from each timestamp, producing values from 0 to 23.
Once the observations are grouped by hour, we can calculate the average absolute movement for each group.
Conceptually, the workflow looks like this:
Hourly observations → Percentage movement → Absolute movement → Group by hour → Compare averages
This reduces hundreds of individual observations to 24 hourly categories that are much easier to compare.
A Simple Python Workflow
A minimal implementation only requires pandas, NumPy and Matplotlib.
The process is straightforward:
- Generate or load timestamped hourly observations.
- Calculate the percentage movement for each observation.
- Convert each movement to its absolute value.
- Extract the hour from each timestamp.
- Group the observations from hour 0 through hour 23.
- Calculate the average absolute movement for each hour.
- Visualize the result as a bar chart.
The result is a simple 24-bar visualization showing how the average magnitude of movement differs across hourly groups.
What Can We Learn From It?
With simulated observations, some hourly averages will naturally be higher than others.
However, there is an important limitation: those differences should not be interpreted as evidence that a particular hour is genuinely more volatile in real markets.
Randomly generated observations contain random variation. A tall bar in this experiment demonstrates how the analysis works, not a persistent market phenomenon.
What is more useful is the workflow itself.
We start with hundreds of timestamped observations, transform them into a consistent measure, group them according to time, and reduce the result to something that can be inspected visually.
The same approach could later be applied to real historical OHLC data.
Extending the Experiment
With a larger real-world dataset, the analysis could explore several additional questions:
- Are certain hours consistently associated with larger price movements?
- Do patterns change when major financial centers become active?
- Are weekends noticeably different from weekdays?
- Is higher trading volume associated with larger movements?
- Do the same hourly patterns appear across different assets?
Instead of looking at only 30 days, a more serious analysis could cover six months, one year, or several years.
Longer periods are particularly useful because a pattern appearing during a few weeks may disappear once more observations are included.
Volume could also be added as another variable. This would make it possible to compare market activity and price movement instead of treating volatility in isolation.
Limitations
This project is intentionally simple.
The observations are simulated, so the dataset should not be used to draw conclusions about the historical behavior of any particular asset.
Absolute percentage movement is also only one way to describe volatility. More detailed studies might use standard deviation, rolling volatility, high-low ranges, realized volatility, or other statistical measures.
Time zones require care as well. Before comparing hourly activity from a real dataset, timestamps should be standardized, typically to UTC, so observations are grouped consistently.
These limitations are part of the point of the experiment: a chart is only as meaningful as the assumptions and data behind it.
24/7 Does Not Mean 24 Identical Hours
The central idea is simple: a market being available 24 hours a day does not mean human activity is evenly distributed across those 24 hours.
Liquidity can change. Participation can change. Trading volume can change. News and economic events occur at particular times, while different regions of the world become active and inactive throughout the day.
So “always open” and “always equally active” are not the same thing.
This small dataset provides a starting point for examining that idea with data rather than assumptions. A future version could replace the simulated observations with real hourly candlestick records, compare multiple assets, incorporate volume, and separate weekdays from weekends.
Sometimes a useful data project can begin with something surprisingly small: ask one clear question, find a way to measure it, and see what the data reveals.
This dataset is intended for educational and data-analysis purposes only. It is not financial or investment advice.
- Downloads last month
- 35