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: 4b004d15b732ff983f6aa198f506712a6d52d6b2505d17e02f1733e2ae43c89c
Tx prefix hash: 8afd50aa6af92f2c7254f8864564256041182c5bcb644b28e07539508c6af7ae
Tx public key: 252259422063c6cec2889755bf7fb9ed14d81014a98282ab29789f77e87fb280
| Timestamp: 1779847497 | Timestamp [UTC]: 2026-05-27 02:04:57 | Age [y:d:h:m:s]: 00:012:23:31:00 |
| Block: 2479 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5407 | RingCT/type: yes/0 |
| Extra: 01252259422063c6cec2889755bf7fb9ed14d81014a98282ab29789f77e87fb28002090000000326697be300 | ||
1 output(s) for total of 35.018468538670 HMNY
| stealth address | amount | amount idx | tag |
| 00: 71a3ef65060e8e94b4a8796e7ffe86ca950aaf81e12454afd6b9e140898c6fcb | 35.018468538670 | 2915 of 0 | <fe> |
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": 2539,
"vin": [ {
"gen": {
"height": 2479
}
}
],
"vout": [ {
"amount": 35018468538670,
"target": {
"tagged_key": {
"key": "71a3ef65060e8e94b4a8796e7ffe86ca950aaf81e12454afd6b9e140898c6fcb",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 37, 34, 89, 66, 32, 99, 198, 206, 194, 136, 151, 85, 191, 127, 185, 237, 20, 216, 16, 20, 169, 130, 130, 171, 41, 120, 159, 119, 232, 127, 178, 128, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}