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: 3313bc2ead949a3665aa5fc7a0c1ceb0722c82bb9729c16a19e6b3c510189f45
Tx prefix hash: 9a93a28d0d16a7f17d6d53a346a4e8e4af175b450e5d8b6bba7e4221b1579229
Tx public key: b34b1533c5fa0ee8dcd4472fc131751554e400903a1704e0e5545e7f8dade309
| Timestamp: 1779802260 | Timestamp [UTC]: 2026-05-26 13:31:00 | Age [y:d:h:m:s]: 00:013:12:04:57 |
| Block: 2312 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5574 | RingCT/type: yes/0 |
| Extra: 01b34b1533c5fa0ee8dcd4472fc131751554e400903a1704e0e5545e7f8dade30902090000000226697be300 | ||
1 output(s) for total of 35.029624661470 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5e76ae13e3f25dfa73c0d566d96a3fe8fa130f1da6240cfa0626bc8c8f975da1 | 35.029624661470 | 2702 of 0 | <52> |
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": 2372,
"vin": [ {
"gen": {
"height": 2312
}
}
],
"vout": [ {
"amount": 35029624661470,
"target": {
"tagged_key": {
"key": "5e76ae13e3f25dfa73c0d566d96a3fe8fa130f1da6240cfa0626bc8c8f975da1",
"view_tag": "52"
}
}
}
],
"extra": [ 1, 179, 75, 21, 51, 197, 250, 14, 232, 220, 212, 71, 47, 193, 49, 117, 21, 84, 228, 0, 144, 58, 23, 4, 224, 229, 84, 94, 127, 141, 173, 227, 9, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}