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: 2c28106b6be50dd93c1fc86b2e5f5b099b379cb4acd81b55c2de4d39a740c272
Tx prefix hash: 3e34ce63956fae4d90b39ae524965b4a9e638a1c94acf99ba4633f0597648474
Tx public key: e8a2a9eef7d829fe2944989b5af774ae45a0b176fb90d339401fe2bf518db814
| Timestamp: 1780712074 | Timestamp [UTC]: 2026-06-06 02:14:34 | Age [y:d:h:m:s]: 00:002:23:21:23 |
| Block: 6163 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1723 | RingCT/type: yes/0 |
| Extra: 01e8a2a9eef7d829fe2944989b5af774ae45a0b176fb90d339401fe2bf518db814020900000001e49593ff00 | ||
1 output(s) for total of 34.773267482368 HMNY
| stealth address | amount | amount idx | tag |
| 00: f5ea792280f80069d01327300dff0917f4c0b1b9f79bfc8738e81c4d5ea53be6 | 34.773267482368 | 7640 of 0 | <fc> |
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": 6223,
"vin": [ {
"gen": {
"height": 6163
}
}
],
"vout": [ {
"amount": 34773267482368,
"target": {
"tagged_key": {
"key": "f5ea792280f80069d01327300dff0917f4c0b1b9f79bfc8738e81c4d5ea53be6",
"view_tag": "fc"
}
}
}
],
"extra": [ 1, 232, 162, 169, 238, 247, 216, 41, 254, 41, 68, 152, 155, 90, 247, 116, 174, 69, 160, 177, 118, 251, 144, 211, 57, 64, 31, 226, 191, 81, 141, 184, 20, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}