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: cc4a20910256979ce34410caa6b0ed09a8726adcf9f0947a9b071e5d4d67e62b
Tx prefix hash: 6f7a1ffa2edbab2a9a4a1c2e7892601b74ad234ced8d5cc7ea4a44ccf4e7b4b5
Tx public key: b5fed3aeff493d427864fbf58a841a192b39defcb1d5e1eb93c470ca27d6af30
| Timestamp: 1780128821 | Timestamp [UTC]: 2026-05-30 08:13:41 | Age [y:d:h:m:s]: 00:009:20:19:21 |
| Block: 4925 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3107 | RingCT/type: yes/0 |
| Extra: 01b5fed3aeff493d427864fbf58a841a192b39defcb1d5e1eb93c470ca27d6af3002090000000126697be300 | ||
1 output(s) for total of 34.855474613629 HMNY
| stealth address | amount | amount idx | tag |
| 00: 50aa4a0cad99a035968a6c157540c59b438c714ef878f863c0482e99a60ce68f | 34.855474613629 | 6252 of 0 | <24> |
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": 4985,
"vin": [ {
"gen": {
"height": 4925
}
}
],
"vout": [ {
"amount": 34855474613629,
"target": {
"tagged_key": {
"key": "50aa4a0cad99a035968a6c157540c59b438c714ef878f863c0482e99a60ce68f",
"view_tag": "24"
}
}
}
],
"extra": [ 1, 181, 254, 211, 174, 255, 73, 61, 66, 120, 100, 251, 245, 138, 132, 26, 25, 43, 57, 222, 252, 177, 213, 225, 235, 147, 196, 112, 202, 39, 214, 175, 48, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}