Reading Bitcoin daily network activity

Two distinct measurements and separate charts

Confirmed transactions are transactions the provider reports as included in blocks. They are neither pending mempool transactions, economic payments, settled value nor people. Unique addresses used are addresses under the source’s definition; a person can use multiple addresses and an address can serve multiple users. These are not counts of wallets, investors or users.

Each chart retains its own unit and scale. Transaction and address counts are not combined, and summing daily addresses would not give period-unique addresses. Lines connect only adjacent available days; gaps have no interpolation, carried-forward value or smoothing. Missing observations are not zero.

The period ends at capture, not the last value

The first visible opening reads two original sources once and applies 90 preceding source days up to the capture date when evidence exists. The provider may return its last value several days earlier; the missing tail remains in the calendar. Cards show the latest available day in the applied period and subsequent days without a usable observation.

The 7, 30 and 90 day buttons only prepare a draft. Custom intervals are start-inclusive, end-exclusive and at most 90 days. Choose one or both metrics and confirm Apply period and metrics. Until then, charts, table and export retain the preceding query. Changing the table page or selecting a point does not change the result.

Complete calendar and exact original point

The calendar retains every selected day, including days wholly absent from the source. It distinguishes an available count, original null, absent day, unavailable source and an unusable negative, non-integer or oversized count. A valid zero remains zero. Select a count or gap in the table; available chart points can also be selected with the keyboard.

Details preserve the original UNIX x, exact y token, source position, native metadata, read start, completed capture, HTTP Date, SHA-256 and whole original response body. For example, 736499.0 can qualify losslessly as integer count 736499; its original spelling remains alongside it. Point dates are source UTC labels. Exact aggregation boundaries, publication, revisions and finality are not independently established.

Refresh and export the same whole result

Automatic polling is off. Refresh original inputs prepares a new set for explicit Apply. Failure or cancellation preserves the preceding result with its original clocks. The six-hour cache starts at each source’s completed capture; it does not prove network freshness or a final daily count.