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: dd368ad3b7be917d9441475d45af306188eaff8f417d14691261ae00da959c40
Tx prefix hash: f2d28422b0ab1793537b471cb0b30ee5ccf2195ba5b509395a6ff1eff8171715
Tx public key: fb9d47c524c8cf8c6f06b3ce27f49bd0c295299aa842d78bcfe69ae0a09c8ce4
| Timestamp: 1780902921 | Timestamp [UTC]: 2026-06-08 07:15:21 | Age [y:d:h:m:s]: 00:000:16:03:32 |
| Block: 7836 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 50 | RingCT/type: yes/0 |
| Extra: 01fb9d47c524c8cf8c6f06b3ce27f49bd0c295299aa842d78bcfe69ae0a09c8ce40209000000024a728a4c00 | ||
1 output(s) for total of 34.662482930124 HMNY
| stealth address | amount | amount idx | tag |
| 00: dde502a17a6a13f6f44942cf8f8db17ffa038d44eeeceeb4e6d88392ad6f90a0 | 34.662482930124 | 9714 of 0 | <c3> |
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": 7896,
"vin": [ {
"gen": {
"height": 7836
}
}
],
"vout": [ {
"amount": 34662482930124,
"target": {
"tagged_key": {
"key": "dde502a17a6a13f6f44942cf8f8db17ffa038d44eeeceeb4e6d88392ad6f90a0",
"view_tag": "c3"
}
}
}
],
"extra": [ 1, 251, 157, 71, 197, 36, 200, 207, 140, 111, 6, 179, 206, 39, 244, 155, 208, 194, 149, 41, 154, 168, 66, 215, 139, 207, 230, 154, 224, 160, 156, 140, 228, 2, 9, 0, 0, 0, 2, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}