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: a76fcb8801af1d197234259bde4d66381bf71632584e05267e18b260168e83fd
Tx prefix hash: e722203b79102d7ef863e634e99a44a120befaf920e3dc4509576f8053d3e77d
Tx public key: d46e35569169fb6b2b1303f2d90f320c9e47945181558ba00c16cf6bef3521f5
| Timestamp: 1779896595 | Timestamp [UTC]: 2026-05-27 15:43:15 | Age [y:d:h:m:s]: 00:012:12:07:43 |
| Block: 3108 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4843 | RingCT/type: yes/0 |
| Extra: 01d46e35569169fb6b2b1303f2d90f320c9e47945181558ba00c16cf6bef3521f502090000000426697be300 | ||
1 output(s) for total of 34.979896452936 HMNY
| stealth address | amount | amount idx | tag |
| 00: 47877ad5d306356d9785d35c2d7eb6f72dc4e562fb23bdda89f89f444d010892 | 34.979896452936 | 3706 of 0 | <8e> |
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": 3168,
"vin": [ {
"gen": {
"height": 3108
}
}
],
"vout": [ {
"amount": 34979896452936,
"target": {
"tagged_key": {
"key": "47877ad5d306356d9785d35c2d7eb6f72dc4e562fb23bdda89f89f444d010892",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 212, 110, 53, 86, 145, 105, 251, 107, 43, 19, 3, 242, 217, 15, 50, 12, 158, 71, 148, 81, 129, 85, 139, 160, 12, 22, 207, 107, 239, 53, 33, 245, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}