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: 27eee75d5b5c1e6057b8c3fe61288d5544c6cbefb94cc6a8f0d6eba217ee4b99
Tx prefix hash: 902c7ab8946351a68ccdf9ad61181d62b879cc53b47ed446e57d1e0c4fd1c0f6
Tx public key: c82e4686e8177c61b5fac6784fc083ceac82d4ae40b1557bbbe85443843ab9fb
| Timestamp: 1779438990 | Timestamp [UTC]: 2026-05-22 08:36:30 | Age [y:d:h:m:s]: 00:017:16:59:27 |
| Block: 197 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7689 | RingCT/type: yes/0 |
| Extra: 01c82e4686e8177c61b5fac6784fc083ceac82d4ae40b1557bbbe85443843ab9fb020900000001f2c813e500 | ||
1 output(s) for total of 35.171221197380 HMNY
| stealth address | amount | amount idx | tag |
| 00: 22c6c57936877bb2e4d1ac4fc19752fa904fcd26a241f3b7cdf2ec32292f2404 | 35.171221197380 | 193 of 0 | <ce> |
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": 257,
"vin": [ {
"gen": {
"height": 197
}
}
],
"vout": [ {
"amount": 35171221197380,
"target": {
"tagged_key": {
"key": "22c6c57936877bb2e4d1ac4fc19752fa904fcd26a241f3b7cdf2ec32292f2404",
"view_tag": "ce"
}
}
}
],
"extra": [ 1, 200, 46, 70, 134, 232, 23, 124, 97, 181, 250, 198, 120, 79, 192, 131, 206, 172, 130, 212, 174, 64, 177, 85, 123, 187, 232, 84, 67, 132, 58, 185, 251, 2, 9, 0, 0, 0, 1, 242, 200, 19, 229, 0
],
"rct_signatures": {
"type": 0
}
}