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: a25146a77c812df47e222f0d97e9270d36160f4700f5f7ac5d29f7a26d75827b
Tx prefix hash: 84603d05b711098767c7a011eaec3a3a153c540406eeacb72c61c7063ddf2153
Tx public key: 0e643658ff31bf16e923293ab31152c98d24a5e656492cd781b987fa89ff523e
| Timestamp: 1780992179 | Timestamp [UTC]: 2026-06-09 08:02:59 | Age [y:d:h:m:s]: 00:006:00:16:36 |
| Block: 8254 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 491 | RingCT/type: yes/0 |
| Extra: 010e643658ff31bf16e923293ab31152c98d24a5e656492cd781b987fa89ff523e020900000001e49593ff00 | ||
1 output(s) for total of 34.634858499651 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9b41e5014fa4cdb174490ffea80cd4a144af4cec7de83ec52eac3fdcc6fab792 | 34.634858499651 | 10216 of 0 | <67> |
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": 8314,
"vin": [ {
"gen": {
"height": 8254
}
}
],
"vout": [ {
"amount": 34634858499651,
"target": {
"tagged_key": {
"key": "9b41e5014fa4cdb174490ffea80cd4a144af4cec7de83ec52eac3fdcc6fab792",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 14, 100, 54, 88, 255, 49, 191, 22, 233, 35, 41, 58, 179, 17, 82, 201, 141, 36, 165, 230, 86, 73, 44, 215, 129, 185, 135, 250, 137, 255, 82, 62, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}