GET
/
api
/
v1
/
developer
/
bitcoin
/
mempool
/
inputs
curl --request GET \
  --url https://api.allium.so/api/v1/developer/bitcoin/mempool/inputs \
  --header 'X-API-KEY: <api-key>'
{
  "items": [
    {
      "spent_transaction_hash": "<string>",
      "spent_output_index": 0,
      "script_asm": "<string>",
      "script_hex": "<string>",
      "sequence": 0,
      "txinwitness": {},
      "index": 0,
      "transaction_hash": "<string>",
      "block_hash": "<string>",
      "block_timestamp": "2023-11-07T05:31:56Z",
      "input_id": "<string>",
      "spent_utxo_id": "<string>",
      "fetched_at": "2023-11-07T05:31:56Z"
    }
  ],
  "size": 2,
  "page": 2
}

Inputs in Bitcoin transactions reference unspent outputs from previous transactions, using them to fund new transfers. Each input must match or exceed the value being spent, with any excess allocated to change or fees. Inputs are consumed in a First-In-First-Out (FIFO) manner, helping track the flow of funds.

Authorizations

​
X-API-KEY
string
header
required

Query Parameters

​
chain
enum<string>
required
Available options:
abstract,
aleph_zero,
alienx,
apechain,
aptos,
arbitrum,
arbitrum_nova,
arbitrum_sepolia,
astar,
avalanche,
b3,
base,
base_sepolia,
beacon,
beacon_validators,
berachain,
binance,
bitcoin,
blast,
bsc,
celo,
cosmos,
cosmoshub,
ethereum,
stellar,
ethereum_goerli,
fantom,
xrp_ledger,
vana,
dydx,
ethereum_sepolia,
kava,
bitcoin_cash,
celestia,
codex,
litecoin,
mantra,
dymension,
babylon,
ethereum_hoodi,
winr,
sx,
injective,
educhain,
dogecoin,
hyperevm,
hyperliquid,
everclear,
fraxtal,
gnosis,
gravity,
harmony,
hedera,
holesky,
imx_zkevm,
ink,
kinto,
linea,
manta_pacific,
mantle,
metis,
mode,
monad_devnet1,
monad_testnet,
near,
oasys,
optimism,
osmosis,
polygon,
polygon_zkevm,
proof_of_play_apex,
proof_of_play_boss,
provenance,
real,
reya,
ronin,
rootstock,
sanko,
scroll,
scroll_sepolia,
sei,
solana,
soneium,
sonic,
stacks,
starknet,
superposition,
sui,
ton,
tron,
unichain,
worldchain,
zksync,
zora
​
fetched_at_gte
string
​
fetched_at_lte
string

Response

200
application/json

Successful Response

The response is of type object.