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: 5c6c285cc37014b0a79ec543f758cb303311fc59b5ae07fd74cc305f9f43ef48
Tx prefix hash: 2f57b04610a8493f602ca4b3ecb9fe9a3a7f9427aee19c8760d57efc998ff9a5
Tx public key: 50d60c39aeefb17dcafcfacdd35a00da6ccbbbf78bb57591f16c1a61a014f541
| Timestamp: 1780835587 | Timestamp [UTC]: 2026-06-07 12:33:07 | Age [y:d:h:m:s]: 00:001:13:02:50 |
| Block: 7401 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 485 | RingCT/type: yes/0 |
| Extra: 0150d60c39aeefb17dcafcfacdd35a00da6ccbbbf78bb57591f16c1a61a014f541020900000002e49593ff00 | ||
1 output(s) for total of 34.691254237792 HMNY
| stealth address | amount | amount idx | tag |
| 00: ac9efec84c23250a2364f48e7bfac308247e3f863f09c65e6b469fe53842e151 | 34.691254237792 | 9113 of 0 | <6f> |
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": 7461,
"vin": [ {
"gen": {
"height": 7401
}
}
],
"vout": [ {
"amount": 34691254237792,
"target": {
"tagged_key": {
"key": "ac9efec84c23250a2364f48e7bfac308247e3f863f09c65e6b469fe53842e151",
"view_tag": "6f"
}
}
}
],
"extra": [ 1, 80, 214, 12, 57, 174, 239, 177, 125, 202, 252, 250, 205, 211, 90, 0, 218, 108, 203, 187, 247, 139, 181, 117, 145, 241, 108, 26, 97, 160, 20, 245, 65, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}