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: 30aa60b7ca85f1b3569a81094924924af3d99abf513ee1f1c369506984b01837
Tx prefix hash: feb50d4383c9eb741531c0bbc5440dd6179d087d004d0bde82243452bbc91e8b
Tx public key: 1ef641ab4f80aa320b846ec39389c8d4f53aaac3ebd3b22007e4845e5278d50a
| Timestamp: 1779915312 | Timestamp [UTC]: 2026-05-27 20:55:12 | Age [y:d:h:m:s]: 00:012:05:54:36 |
| Block: 3293 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4627 | RingCT/type: yes/0 |
| Extra: 011ef641ab4f80aa320b846ec39389c8d4f53aaac3ebd3b22007e4845e5278d50a02090000000226697be300 | ||
1 output(s) for total of 34.964141634788 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1196e978c98d4e2b9182e56262c5fec4c734ba1674249f929d9a5fed5217c10c | 34.964141634788 | 3955 of 0 | <86> |
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": 3353,
"vin": [ {
"gen": {
"height": 3293
}
}
],
"vout": [ {
"amount": 34964141634788,
"target": {
"tagged_key": {
"key": "1196e978c98d4e2b9182e56262c5fec4c734ba1674249f929d9a5fed5217c10c",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 30, 246, 65, 171, 79, 128, 170, 50, 11, 132, 110, 195, 147, 137, 200, 212, 245, 58, 170, 195, 235, 211, 178, 32, 7, 228, 132, 94, 82, 120, 213, 10, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}