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: ecdf035f44d09cd5b17412107dc01d6cd585a13fbd3addda7df62bd9c0a67a1f
Tx prefix hash: c0884191a140be6356dd03e6b83daa858b5ac7d92c0073761539e7896765a877
Tx public key: d458e4c7d07e1556073cf1217d426068d512c1962c12168393bdb3ba6af9f023
| Timestamp: 1780852186 | Timestamp [UTC]: 2026-06-07 17:09:46 | Age [y:d:h:m:s]: 00:001:06:09:07 |
| Block: 7547 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 339 | RingCT/type: yes/0 |
| Extra: 01d458e4c7d07e1556073cf1217d426068d512c1962c12168393bdb3ba6af9f023020900000001e49593ff00 | ||
1 output(s) for total of 34.684213399375 HMNY
| stealth address | amount | amount idx | tag |
| 00: 119a1f1b182e70e27412539bcc553eae40c2b65f8b707945db1f4fce3d678f1d | 34.684213399375 | 9313 of 0 | <51> |
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": 7607,
"vin": [ {
"gen": {
"height": 7547
}
}
],
"vout": [ {
"amount": 34684213399375,
"target": {
"tagged_key": {
"key": "119a1f1b182e70e27412539bcc553eae40c2b65f8b707945db1f4fce3d678f1d",
"view_tag": "51"
}
}
}
],
"extra": [ 1, 212, 88, 228, 199, 208, 126, 21, 86, 7, 60, 241, 33, 125, 66, 96, 104, 213, 18, 193, 150, 44, 18, 22, 131, 147, 189, 179, 186, 106, 249, 240, 35, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}