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: af593390d5fde4cfbbe21648ef10b2fccb1c17d41b7f4ee6482be57eb45e4bc2
Tx prefix hash: 770e692eabac60c9240e6198086f7e18f06c0fc4406e31779b809d186a060cab
Tx public key: d834875562912046c2df67afe532af2bb823b8472553f64bd51fb0d2d1827487
| Timestamp: 1779437450 | Timestamp [UTC]: 2026-05-22 08:10:50 | Age [y:d:h:m:s]: 00:017:17:25:07 |
| Block: 163 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7723 | RingCT/type: yes/0 |
| Extra: 01d834875562912046c2df67afe532af2bb823b8472553f64bd51fb0d2d1827487020900000002a662ed0300 | ||
1 output(s) for total of 35.173502122055 HMNY
| stealth address | amount | amount idx | tag |
| 00: 30d7b6db78a0032a16411f64f3a325074e0cb54b5e5d020564a736255c8390eb | 35.173502122055 | 159 of 0 | <ee> |
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": 223,
"vin": [ {
"gen": {
"height": 163
}
}
],
"vout": [ {
"amount": 35173502122055,
"target": {
"tagged_key": {
"key": "30d7b6db78a0032a16411f64f3a325074e0cb54b5e5d020564a736255c8390eb",
"view_tag": "ee"
}
}
}
],
"extra": [ 1, 216, 52, 135, 85, 98, 145, 32, 70, 194, 223, 103, 175, 229, 50, 175, 43, 184, 35, 184, 71, 37, 83, 246, 75, 213, 31, 176, 210, 209, 130, 116, 135, 2, 9, 0, 0, 0, 2, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}