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: 297c7488330fe82d498f9bc5511976b2c659e3595c0cfef7d28b34a0c22747eb
Tx prefix hash: c359df848d28381323cea75e775518b2c9f614b87be0c1ad0a41e6746284e3ad
Tx public key: afde8ccd13715283433b07a4782429214606e8e6b19a308a70e3750c4d4ae7d5
| Timestamp: 1779633550 | Timestamp [UTC]: 2026-05-24 14:39:10 | Age [y:d:h:m:s]: 00:015:10:56:47 |
| Block: 992 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6894 | RingCT/type: yes/0 |
| Extra: 01afde8ccd13715283433b07a4782429214606e8e6b19a308a70e3750c4d4ae7d5020900000001ba6d17be00 | ||
1 output(s) for total of 35.117929955018 HMNY
| stealth address | amount | amount idx | tag |
| 00: 02441d2150caf6671abeb3e57c81085fd117d0bed10e7693e40bdf8105bf0343 | 35.117929955018 | 1128 of 0 | <d2> |
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": 1052,
"vin": [ {
"gen": {
"height": 992
}
}
],
"vout": [ {
"amount": 35117929955018,
"target": {
"tagged_key": {
"key": "02441d2150caf6671abeb3e57c81085fd117d0bed10e7693e40bdf8105bf0343",
"view_tag": "d2"
}
}
}
],
"extra": [ 1, 175, 222, 140, 205, 19, 113, 82, 131, 67, 59, 7, 164, 120, 36, 41, 33, 70, 6, 232, 230, 177, 154, 48, 138, 112, 227, 117, 12, 77, 74, 231, 213, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}