This article was published 4 years ago. Some details may no longer reflect current market conditions or recent developments.If you spot anything that needs an update, contact us.
Cover art/illustration via CryptoSlate. Image includes combined content which may include the use of AI tools.
Glassnode data analyzed by Cryptoslate revealed that the number of active Ethereum (ETH) addresses reached a new all-time high (ATH) on Dec. 9.
Active ETH addresses
The blue line on the chart above represents the active ETH addresses since January 2018. On Dec. 9, the number of active addresses spiked to reach 1.4 million. The previous ATH before this was recorded at the end of July at just above 1 million.
Breakdown
Looking at specific transaction types on Dec. 9, CryptoSlate analysts revealed huge movements in stablecoins and ERC20 transactions.
ERC20
This category includes all transactions that initiateERC20 contracts, excluding the contracts in the Stablecoins category. The chart below represents the volume of these transactions with the purple areas.
ETH addresses ERC20 transactions
The data demonstrate a visible spike in the number of ERC20 transactions on Dec.9, which marks a new ATH for the category. The previous ATH level was recorded in early August at just above 20%.
The term stablecoins refer to fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. This category includes over 150 stablecoins, with Tether (USDT), USD Coin (USDC), Terra Classic (UST), Binance USD (BUSD), and DAI (DAI) being the most prominent ones.
ETH addresses stablecoin transactions
The chart above reflects the size of stablecoin transactions to and from ETH addresses. Although it didn't record a new ATH, the number of stablecoin transactions spiked on the given date. The ATH for this category was recorded in the second half of May.
CryptoSlate Daily Brief
Daily signals, zero noise.
Market-moving headlines and context delivered every morning in one tight read.
5-minute digest 100k+ readers
Free. No spam. Unsubscribe any time.
Whoops, looks like there was a problem. Please try again.
You’re subscribed. Welcome aboard.
Other transactions
This category includes all other transactions on the ETH network that are not included in either of the categories above.
The chart below visualizes the number of other transactions with the pink areas since the beginning of the year.
ETH addresses other transactions
After a significant fall in mid-October, the volume of this category started to increase steadily with some volatility. The volume of this category also recorded a new ATH in early December at just above 52%.
The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic
session
__cfseq
Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
session
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
_cfuvid
The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.
session
__cflb
When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool.
session
__cf_bm
Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions.
session
__cfruid
Used by the content network, Cloudflare, to identify trusted web traffic.
session
cf_chl_rc_m
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_ni
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_i
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
__cfwaitingroom
The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active.
session
cf_use_ob
The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds.
session
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gid
ID used to identify users for 24 hours after last activity
24 hours
_ga_
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga
ID used to identify users
2 years
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utma
ID used to identify users and sessions
2 years after last activity
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Clarity is a web analytics service that tracks and reports website traffic.