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: e9974a18a0d21438d20bfc797e02e56b3555f7372c4277af4a0316b726674841
Tx prefix hash: 291c5ac9e86f0a098657f6493a687974b9dbd4f105e9653c7c568ee7cb8a52a1
Tx public key: bd6af1663676d930044e8f6f4a813aff69c0eec7ab48e5dc85a3b38e867b8249
| Timestamp: 1779470959 | Timestamp [UTC]: 2026-05-22 17:29:19 | Age [y:d:h:m:s]: 00:017:09:20:29 |
| Block: 564 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7356 | RingCT/type: yes/0 |
| Extra: 01bd6af1663676d930044e8f6f4a813aff69c0eec7ab48e5dc85a3b38e867b824902090000000493369e7d00 | ||
1 output(s) for total of 35.146610041276 HMNY
| stealth address | amount | amount idx | tag |
| 00: a7128f217232564d19175309123ddf78a5c545aa080869e65764cba0ad042f67 | 35.146610041276 | 572 of 0 | <1e> |
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": 624,
"vin": [ {
"gen": {
"height": 564
}
}
],
"vout": [ {
"amount": 35146610041276,
"target": {
"tagged_key": {
"key": "a7128f217232564d19175309123ddf78a5c545aa080869e65764cba0ad042f67",
"view_tag": "1e"
}
}
}
],
"extra": [ 1, 189, 106, 241, 102, 54, 118, 217, 48, 4, 78, 143, 111, 74, 129, 58, 255, 105, 192, 238, 199, 171, 72, 229, 220, 133, 163, 179, 142, 134, 123, 130, 73, 2, 9, 0, 0, 0, 4, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}