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: 4f37d54c9af43b168319bdc1d6a16076e511ceb0fd8057ed287679705878ff0b
Tx prefix hash: 924b335506112a51c5fbbbdfde2f814831e43fa9bb957c06ce8fb30f3220fe52
Tx public key: fe03d81a2799cb341784d4b2957da3924c150e51b00b6fccb0d59141cb878276
| Timestamp: 1779433652 | Timestamp [UTC]: 2026-05-22 07:07:32 | Age [y:d:h:m:s]: 00:017:18:28:25 |
| Block: 48 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0908 kB |
| Tx version: 2 | No of confirmations: 7838 | RingCT/type: yes/0 |
| Extra: 01fe03d81a2799cb341784d4b2957da3924c150e51b00b6fccb0d59141cb878276020900000001a662ed0300 | ||
1 output(s) for total of 35.181218110701 HMNY
| stealth address | amount | amount idx | tag |
| 00: 931f0e363a1b414c765c4b655bc338da8f68e732bf4b982c51e48ff41fe7417c | 35.181218110701 | 44 of 0 | <ac> |
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": 108,
"vin": [ {
"gen": {
"height": 48
}
}
],
"vout": [ {
"amount": 35181218110701,
"target": {
"tagged_key": {
"key": "931f0e363a1b414c765c4b655bc338da8f68e732bf4b982c51e48ff41fe7417c",
"view_tag": "ac"
}
}
}
],
"extra": [ 1, 254, 3, 216, 26, 39, 153, 203, 52, 23, 132, 212, 178, 149, 125, 163, 146, 76, 21, 14, 81, 176, 11, 111, 204, 176, 213, 145, 65, 203, 135, 130, 118, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}