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: b39d11e0c79bebeb50e954be82657f815efe5fac3bfa9500d885fe1c0d951fe2
Tx prefix hash: 1b91f057520d5ee2877c80ea25205d40462af61ff0673645ef2544f762398879
Tx public key: 4a990fd4e35a36bfd850a86518ed3918d2a7d99e6addb3f48bb310a9e277ef93
| Timestamp: 1780719146 | Timestamp [UTC]: 2026-06-06 04:12:26 | Age [y:d:h:m:s]: 00:002:22:28:10 |
| Block: 6226 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1671 | RingCT/type: yes/0 |
| Extra: 014a990fd4e35a36bfd850a86518ed3918d2a7d99e6addb3f48bb310a9e277ef93020900000001e49593ff00 | ||
1 output(s) for total of 34.769089270537 HMNY
| stealth address | amount | amount idx | tag |
| 00: f790cab09f54c9c44a28289faceca5c4196d1f8662c7e71e9ceb7a10d98fb326 | 34.769089270537 | 7705 of 0 | <e6> |
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": 6286,
"vin": [ {
"gen": {
"height": 6226
}
}
],
"vout": [ {
"amount": 34769089270537,
"target": {
"tagged_key": {
"key": "f790cab09f54c9c44a28289faceca5c4196d1f8662c7e71e9ceb7a10d98fb326",
"view_tag": "e6"
}
}
}
],
"extra": [ 1, 74, 153, 15, 212, 227, 90, 54, 191, 216, 80, 168, 101, 24, 237, 57, 24, 210, 167, 217, 158, 106, 221, 179, 244, 139, 179, 16, 169, 226, 119, 239, 147, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}