Head slot/epoch, epoch clock, finality lag, sync health

Extraits de code

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

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

$ch = curl_init("https://api.oanor.com/beaconchain-api/v1/status");
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/beaconchain-api/v1/status",
    headers={"x-oanor-key": "oanor_test_..."}
)

Exemple de réponse

Une réponse réelle de ce endpoint, capturée lors du dernier contrôle de santé.

{
    "data": {
        "note": "The Beacon Chain's live consensus state. head_slot/head_epoch are where the chain is now; epoch_progress_pct and seconds_to_next_epoch are the epoch clock (one epoch ≈ 6.4 minutes). finalized_epoch is the last epoch the validators irreversibly finalized; finality_lag_epochs is how many epochs the head is ahead of it — a lag of about two is healthy, and is_finalizing flags whether finality is keeping up (a stalled finality is a network emergency). Live, cached ~30s.",
        "source": "public Ethereum consensus-layer (Beacon) API, keyless",
        "head_slot": 14541812,
        "head_epoch": 454431,
        "is_syncing": false,
        "is_finalizing": true,
        "is_optimistic": true,
        "slot_in_epoch": 20,
        "sync_distance": 0,
        "connected_peers": 203,
        "finalized_epoch": 454429,
        "justified_epoch": 454430,
        "epoch_progress_pct": 62.5,
        "finality_lag_epochs": 2,
        "seconds_to_next_epoch": 138
    },
    "meta": {
        "timestamp": "2026-06-13T04:42:53.577Z",
        "request_id": "f1938611-9c97-41e1-88ad-d36948693d6e"
    },
    "status": "ok",
    "message": "Status retrieved successfully",
    "success": true
}