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: aff71a4475e784cd4f45c70b8db69ccf5308aae45174e5741f1c495f7efdc8f7
Tx prefix hash: 404eb27a970770b25759aa06c888a507795cdbb51ab17f194b2be652f4e8b62c
Tx public key: a1594ab1d1c94396b215366cd894bce1d90c4438bb935332faea71b9e8994177
| Timestamp: 1780697554 | Timestamp [UTC]: 2026-06-05 22:12:34 | Age [y:d:h:m:s]: 00:003:03:23:23 |
| Block: 6013 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1873 | RingCT/type: yes/0 |
| Extra: 01a1594ab1d1c94396b215366cd894bce1d90c4438bb935332faea71b9e8994177020900000002e49593ff00 | ||
1 output(s) for total of 34.783217626797 HMNY
| stealth address | amount | amount idx | tag |
| 00: 514857737f9c463b3757e6f0030ad6488982f501b9e9e968caa029fb4a6aeb3c | 34.783217626797 | 7480 of 0 | <77> |
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": 6073,
"vin": [ {
"gen": {
"height": 6013
}
}
],
"vout": [ {
"amount": 34783217626797,
"target": {
"tagged_key": {
"key": "514857737f9c463b3757e6f0030ad6488982f501b9e9e968caa029fb4a6aeb3c",
"view_tag": "77"
}
}
}
],
"extra": [ 1, 161, 89, 74, 177, 209, 201, 67, 150, 178, 21, 54, 108, 216, 148, 188, 225, 217, 12, 68, 56, 187, 147, 83, 50, 250, 234, 113, 185, 232, 153, 65, 119, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}