Distinguish a pooled Monero key image from a confirmed spend
An integration tracking known key images needs three states rather than a spent/unspent boolean. A spend seen only in a node's pool can disappear or later confirm.
Preserve the input ordering
Replace the two tokens with valid hexadecimal key images and query your own daemon. The response's spent_status entries correspond to request order. A public daemon learns which images you queried together. POST this example to /is_key_image_spent on monerod.
{
"key_images": [
"<first key image>",
"<second key image>"
]
}
Persist transitions explicitly
A result of [2,1] means the first image is spent in the observed transaction pool and the second is spent on chain. Zero means the queried image is unspent in this view. Requery pending records at a later tip. The endpoint reports key-image state and does not identify the receiving address.