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: cb97c3b99879f3d279670acb3b3008bf1cf58847442de178f22300ff6b6dda7e
Tx prefix hash: d29bec8ec36a00ef3946e249542e7912f494e7f09f5d1ff87c94ec3ec6926049
Tx public key: a1478fa70136cac0382d6827a1bbd20c285b5c8f5ea5d18419ea0f466e14d9e6
| Timestamp: 1779723782 | Timestamp [UTC]: 2026-05-25 15:43:02 | Age [y:d:h:m:s]: 00:014:09:52:55 |
| Block: 1808 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6078 | RingCT/type: yes/0 |
| Extra: 01a1478fa70136cac0382d6827a1bbd20c285b5c8f5ea5d18419ea0f466e14d9e6020900000002ba6d17be00 | ||
1 output(s) for total of 35.063314992505 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2b89c08c6ddda505267865276e71cbfaffcc85b07eb544ddd2467017ec14fc11 | 35.063314992505 | 2000 of 0 | <37> |
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": 1868,
"vin": [ {
"gen": {
"height": 1808
}
}
],
"vout": [ {
"amount": 35063314992505,
"target": {
"tagged_key": {
"key": "2b89c08c6ddda505267865276e71cbfaffcc85b07eb544ddd2467017ec14fc11",
"view_tag": "37"
}
}
}
],
"extra": [ 1, 161, 71, 143, 167, 1, 54, 202, 192, 56, 45, 104, 39, 161, 187, 210, 12, 40, 91, 92, 143, 94, 165, 209, 132, 25, 234, 15, 70, 110, 20, 217, 230, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}