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: 358bb16df2a91d0b80379a733dee2fcad031726368838cbf80ed096371d1fc87
Tx prefix hash: eb16388ef2b14e38ed7030f7231e70dcbdd1e65c4c4e98c8e258a57e63a1a95f
Tx public key: d8867ce98e7ae3353b9d7f0d5347196125011d2eb0ac0f86257c0eacc559318b
| Timestamp: 1779862336 | Timestamp [UTC]: 2026-05-27 06:12:16 | Age [y:d:h:m:s]: 00:012:20:28:20 |
| Block: 2699 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5198 | RingCT/type: yes/0 |
| Extra: 01d8867ce98e7ae3353b9d7f0d5347196125011d2eb0ac0f86257c0eacc559318b02090000000126697be300 | ||
1 output(s) for total of 35.003777273045 HMNY
| stealth address | amount | amount idx | tag |
| 00: 70eb96a585af856d1ac580520b659118dae582396377680858986afc48848773 | 35.003777273045 | 3185 of 0 | <16> |
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": 2759,
"vin": [ {
"gen": {
"height": 2699
}
}
],
"vout": [ {
"amount": 35003777273045,
"target": {
"tagged_key": {
"key": "70eb96a585af856d1ac580520b659118dae582396377680858986afc48848773",
"view_tag": "16"
}
}
}
],
"extra": [ 1, 216, 134, 124, 233, 142, 122, 227, 53, 59, 157, 127, 13, 83, 71, 25, 97, 37, 1, 29, 46, 176, 172, 15, 134, 37, 124, 14, 172, 197, 89, 49, 139, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}