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: 0d12c3d15ff06049f80fca399c5df06c76e7ce091df01272d7ba0ae3254cc43c
Tx prefix hash: cb21ccfec2490cc29da3536f9fbf6340f8deaabc317799f3e84763bf0622c131
Tx public key: b35b596b848d8eb64e011649292412cd79d762f54971279b626b7fb371766a50
| Timestamp: 1780814434 | Timestamp [UTC]: 2026-06-07 06:40:34 | Age [y:d:h:m:s]: 00:001:18:06:13 |
| Block: 7039 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 847 | RingCT/type: yes/0 |
| Extra: 01b35b596b848d8eb64e011649292412cd79d762f54971279b626b7fb371766a50020900000002e49593ff00 | ||
1 output(s) for total of 34.715215462342 HMNY
| stealth address | amount | amount idx | tag |
| 00: 71b803b5612951f3f4721a4ef1da6879855c3fc43421b0800d5f146eb9edf199 | 34.715215462342 | 8681 of 0 | <3e> |
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": 7099,
"vin": [ {
"gen": {
"height": 7039
}
}
],
"vout": [ {
"amount": 34715215462342,
"target": {
"tagged_key": {
"key": "71b803b5612951f3f4721a4ef1da6879855c3fc43421b0800d5f146eb9edf199",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 179, 91, 89, 107, 132, 141, 142, 182, 78, 1, 22, 73, 41, 36, 18, 205, 121, 215, 98, 245, 73, 113, 39, 155, 98, 107, 127, 179, 113, 118, 106, 80, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}