For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: d75ff2aac2e469118b45bb94a2288a5bad1cbe86bc415ddb9b97223f67642ead
Tx prefix hash: 9af03790eea5e0ecc67c11e5c036555f7c832f5b9aa148ebd23e0b9af9e5d8b0
Tx public key: 18cba61300ef637849b0b05987a5804727f977b05239bfe0a2d0a6b5e26d05a6
| Timestamp: 1779630169 | Timestamp [UTC]: 2026-05-24 13:42:49 | Age [y:d:h:m:s]: 00:015:11:53:08 |
| Block: 864 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7022 | RingCT/type: yes/0 |
| Extra: 0118cba61300ef637849b0b05987a5804727f977b05239bfe0a2d0a6b5e26d05a6020900000001ba6d17be00 | ||
1 output(s) for total of 35.126504723246 HMNY
| stealth address | amount | amount idx | tag |
| 00: 206691b53190a5fe6f296694a22a483f237ed8b565315ea45068ba2aae4020dc | 35.126504723246 | 996 of 0 | <aa> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 924,
"vin": [ {
"gen": {
"height": 864
}
}
],
"vout": [ {
"amount": 35126504723246,
"target": {
"tagged_key": {
"key": "206691b53190a5fe6f296694a22a483f237ed8b565315ea45068ba2aae4020dc",
"view_tag": "aa"
}
}
}
],
"extra": [ 1, 24, 203, 166, 19, 0, 239, 99, 120, 73, 176, 176, 89, 135, 165, 128, 71, 39, 249, 119, 176, 82, 57, 191, 224, 162, 208, 166, 181, 226, 109, 5, 166, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}