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: 1c8823f2c6e55b61c5fdca9769c1906e0b97e530a306f944b4dfef007a31357a
Tx prefix hash: c18ac23ebebc48d255b69755791771b0ef60fd4d9b735c32b468cf06616e9862
Tx public key: a5f1973901fc4bb514ecf811db1a044cbfc07721e91dd56adef469b7fd3cca95
| Timestamp: 1779847037 | Timestamp [UTC]: 2026-05-27 01:57:17 | Age [y:d:h:m:s]: 00:013:02:35:45 |
| Block: 2474 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5553 | RingCT/type: yes/0 |
| Extra: 01a5f1973901fc4bb514ecf811db1a044cbfc07721e91dd56adef469b7fd3cca9502090000000126697be300 | ||
1 output(s) for total of 35.018802502721 HMNY
| stealth address | amount | amount idx | tag |
| 00: 21b3c0a257200e73e8f6fee9d91cd18d756898d0346569dcbf46a3a16170f02c | 35.018802502721 | 2908 of 0 | <67> |
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": 2534,
"vin": [ {
"gen": {
"height": 2474
}
}
],
"vout": [ {
"amount": 35018802502721,
"target": {
"tagged_key": {
"key": "21b3c0a257200e73e8f6fee9d91cd18d756898d0346569dcbf46a3a16170f02c",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 165, 241, 151, 57, 1, 252, 75, 181, 20, 236, 248, 17, 219, 26, 4, 76, 191, 192, 119, 33, 233, 29, 213, 106, 222, 244, 105, 183, 253, 60, 202, 149, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}