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: aff47a1ee658c555ed31be914aaeeefff2153ec27dd17f7f3e78c0a30fe16662
Tx prefix hash: 398b5c55cbf2bc87eb32c75f552bd7021025fdff254b76ed119e80277825d80c
Tx public key: 996cce602aee38df2cd42c27429d63f5844cd93106a6b8b1d6ad2941897c322e
| Timestamp: 1780774073 | Timestamp [UTC]: 2026-06-06 19:27:53 | Age [y:d:h:m:s]: 00:002:05:18:54 |
| Block: 6696 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1190 | RingCT/type: yes/0 |
| Extra: 01996cce602aee38df2cd42c27429d63f5844cd93106a6b8b1d6ad2941897c322e020900000001e49593ff00 | ||
1 output(s) for total of 34.737934323203 HMNY
| stealth address | amount | amount idx | tag |
| 00: 32cac024405bb2a86f5cc8a03c768d27c2ecbc5427416291d9cd6575d120e4f0 | 34.737934323203 | 8258 of 0 | <7a> |
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": 6756,
"vin": [ {
"gen": {
"height": 6696
}
}
],
"vout": [ {
"amount": 34737934323203,
"target": {
"tagged_key": {
"key": "32cac024405bb2a86f5cc8a03c768d27c2ecbc5427416291d9cd6575d120e4f0",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 153, 108, 206, 96, 42, 238, 56, 223, 44, 212, 44, 39, 66, 157, 99, 245, 132, 76, 217, 49, 6, 166, 184, 177, 214, 173, 41, 65, 137, 124, 50, 46, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}