Exit queue breakdown (voluntary + slashed)

Codefragmenten

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

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

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

Voorbeeldrespons

Een echte respons van dit endpoint, vastgelegd bij de laatste health check.

{
    "data": {
        "note": "The Ethereum exit queue. eth_waiting / validators_waiting are validators voluntarily exiting and churning out at the exit churn limit; slashed_exiting are validators being forced out by slashing (a separate, penalised exit). earliest/latest_exit_epoch come from the validator records. est_clear_hours estimates how long the exiting ETH takes to clear at the current churn limit of 256 ETH/epoch. Live, cached ~90s.",
        "epoch": 454431,
        "source": "Ethereum Beacon API (ethereum-beacon-api.publicnode.com), keyless",
        "eth_waiting": 128.02,
        "est_clear_hours": 0.1,
        "slashed_exiting": {
            "eth": 0,
            "validators": 0
        },
        "latest_exit_epoch": 454434,
        "earliest_exit_time": "2026-06-13T04:57:59.000Z",
        "validators_waiting": 4,
        "earliest_exit_epoch": 454434,
        "churn_limit_eth_per_epoch": 256
    },
    "meta": {
        "timestamp": "2026-06-13T04:42:43.296Z",
        "request_id": "545e1a1f-0c9a-4203-aecf-f74cfec74a56"
    },
    "status": "ok",
    "message": "Exit queue retrieved successfully",
    "success": true
}