Current difficulty + next-adjustment countdown

Code-Snippets

curl "https://api.oanor.com/hashrate-api/v1/difficulty" \
  -H "x-oanor-key: oanor_test_..."

await fetch("https://api.oanor.com/hashrate-api/v1/difficulty", {
  headers: { "x-oanor-key": "oanor_test_..." }
});

$ch = curl_init("https://api.oanor.com/hashrate-api/v1/difficulty");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);

import requests
requests.get(
    "https://api.oanor.com/hashrate-api/v1/difficulty",
    headers={"x-oanor-key": "oanor_test_..."}
)

Beispiel-Response

Echte Antwort dieses Endpoints, erfasst beim letzten Health-Check.

{
    "data": {
        "note": "Bitcoin's mining difficulty and the live difficulty-adjustment countdown. Bitcoin retargets difficulty every 2016 blocks (~2 weeks) so blocks average ~10 minutes: epoch_progress_pct is how far through the current epoch we are, estimated_change_pct the projected size of the next adjustment (positive = mining gets harder), remaining_blocks how many until the retarget, and avg_block_time_seconds the realised block time this epoch (under 600s pushes difficulty up). Live, cached ~60s.",
        "source": "mempool.space public API (v1/difficulty-adjustment), keyless",
        "direction": "easier",
        "remaining_blocks": 160,
        "current_difficulty": 138955357012247.3,
        "epoch_progress_pct": 92.06,
        "previous_change_pct": 1.72,
        "estimated_change_pct": -10.32,
        "next_retarget_height": 953568,
        "avg_block_time_seconds": 669,
        "estimated_retarget_date": "2026-06-14T01:20:55.640Z",
        "current_difficulty_trillions": 138.96
    },
    "meta": {
        "timestamp": "2026-06-12T19:35:55.505Z",
        "request_id": "bae52145-4bdd-409b-aca7-60fc57defa5d"
    },
    "status": "ok",
    "message": "Difficulty retrieved successfully",
    "success": true
}