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: ed47196bda70f3f671c3344d50a00facb111b016790a29b9c47b97eb333004b0
Tx prefix hash: ac3d9718bd72d7f895ddd2aa09dc28e5fb4a34170a913e3a896b3cb1f655c2b5
Tx public key: c8f6ce37422994a580a9099c140b565a1d11fc1d826571273cedb7b6d71f1bdf
| Timestamp: 1779630145 | Timestamp [UTC]: 2026-05-24 13:42:25 | Age [y:d:h:m:s]: 00:015:11:53:32 |
| Block: 861 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7025 | RingCT/type: yes/0 |
| Extra: 01c8f6ce37422994a580a9099c140b565a1d11fc1d826571273cedb7b6d71f1bdf020900000001ba6d17be00 | ||
1 output(s) for total of 35.126705719485 HMNY
| stealth address | amount | amount idx | tag |
| 00: f5f86ae73250d84d72839d61c3ce4247cd15e2d2dd556f0f05d1bf95ab66007d | 35.126705719485 | 993 of 0 | <bc> |
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": 921,
"vin": [ {
"gen": {
"height": 861
}
}
],
"vout": [ {
"amount": 35126705719485,
"target": {
"tagged_key": {
"key": "f5f86ae73250d84d72839d61c3ce4247cd15e2d2dd556f0f05d1bf95ab66007d",
"view_tag": "bc"
}
}
}
],
"extra": [ 1, 200, 246, 206, 55, 66, 41, 148, 165, 128, 169, 9, 156, 20, 11, 86, 90, 29, 17, 252, 29, 130, 101, 113, 39, 60, 237, 183, 182, 215, 31, 27, 223, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}