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: 2dd3776baf6b2d5eb142ece069a019c4dbebf7ae40ca20cb542311b84be8f1bb
Tx prefix hash: 274268388129eafde5326ed160183d985949bcd8ec04037c88ed751aa1bc6648
Tx public key: ffe0c760db3c0d2d21f918dc7e4feffc11d286bbd85bcfc34fbfb9255c2bd10a
| Timestamp: 1779438602 | Timestamp [UTC]: 2026-05-22 08:30:02 | Age [y:d:h:m:s]: 00:017:17:05:55 |
| Block: 193 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7693 | RingCT/type: yes/0 |
| Extra: 01ffe0c760db3c0d2d21f918dc7e4feffc11d286bbd85bcfc34fbfb9255c2bd10a0209000000025cddc08000 | ||
1 output(s) for total of 35.171489533782 HMNY
| stealth address | amount | amount idx | tag |
| 00: ec6e0e3a4b61a9afa58dd13b81d74d1d515f039b94c2590bf7b5564e8ee6cc41 | 35.171489533782 | 189 of 0 | <8f> |
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": 253,
"vin": [ {
"gen": {
"height": 193
}
}
],
"vout": [ {
"amount": 35171489533782,
"target": {
"tagged_key": {
"key": "ec6e0e3a4b61a9afa58dd13b81d74d1d515f039b94c2590bf7b5564e8ee6cc41",
"view_tag": "8f"
}
}
}
],
"extra": [ 1, 255, 224, 199, 96, 219, 60, 13, 45, 33, 249, 24, 220, 126, 79, 239, 252, 17, 210, 134, 187, 216, 91, 207, 195, 79, 191, 185, 37, 92, 43, 209, 10, 2, 9, 0, 0, 0, 2, 92, 221, 192, 128, 0
],
"rct_signatures": {
"type": 0
}
}