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: a1cf646d7c9ff27a5657fe99aaf1464840ea1adc6c1ac61df86f7ad1556524e2
Tx prefix hash: 7b2c7076f690c9ae4f71193756cce739d24d506d444244f68259f471a5f5c02b
Tx public key: b14c8759bbf9cf5c2be397f789fb65780c6d0dabc1967684a223089e7a3b8455
| Timestamp: 1779729871 | Timestamp [UTC]: 2026-05-25 17:24:31 | Age [y:d:h:m:s]: 00:014:12:14:08 |
| Block: 1874 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6259 | RingCT/type: yes/0 |
| Extra: 01b14c8759bbf9cf5c2be397f789fb65780c6d0dabc1967684a223089e7a3b8455020900000001ba6d17be00 | ||
1 output(s) for total of 35.058901320359 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0ba5deee848da4a71f67f72c14910b70904725633cbb37c8d19e44e551e3bf6d | 35.058901320359 | 2087 of 0 | <41> |
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": 1934,
"vin": [ {
"gen": {
"height": 1874
}
}
],
"vout": [ {
"amount": 35058901320359,
"target": {
"tagged_key": {
"key": "0ba5deee848da4a71f67f72c14910b70904725633cbb37c8d19e44e551e3bf6d",
"view_tag": "41"
}
}
}
],
"extra": [ 1, 177, 76, 135, 89, 187, 249, 207, 92, 43, 227, 151, 247, 137, 251, 101, 120, 12, 109, 13, 171, 193, 150, 118, 132, 162, 35, 8, 158, 122, 59, 132, 85, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}