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: 65152051934c553c187c16e0682f4c615873c4fbf1c382b1758dc57f471b5a82
Tx prefix hash: 53c71a44d4610427a2aa311907317f085b53b03a056c157d3f09d8148daacd48
Tx public key: 30498e3fd65c17e06056e4171e4c43a0ffc60d8e621cdab42961da4ce0e75663
| Timestamp: 1780869149 | Timestamp [UTC]: 2026-06-07 21:52:29 | Age [y:d:h:m:s]: 00:001:01:26:24 |
| Block: 7693 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 193 | RingCT/type: yes/0 |
| Extra: 0130498e3fd65c17e06056e4171e4c43a0ffc60d8e621cdab42961da4ce0e75663020900000001e49593ff00 | ||
1 output(s) for total of 34.679368850422 HMNY
| stealth address | amount | amount idx | tag |
| 00: 625e9744047b02475e278d43a4ebac01c5749e49c373f3297634237d50aae09e | 34.679368850422 | 9515 of 0 | <77> |
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": 7753,
"vin": [ {
"gen": {
"height": 7693
}
}
],
"vout": [ {
"amount": 34679368850422,
"target": {
"tagged_key": {
"key": "625e9744047b02475e278d43a4ebac01c5749e49c373f3297634237d50aae09e",
"view_tag": "77"
}
}
}
],
"extra": [ 1, 48, 73, 142, 63, 214, 92, 23, 224, 96, 86, 228, 23, 30, 76, 67, 160, 255, 198, 13, 142, 98, 28, 218, 180, 41, 97, 218, 76, 224, 231, 86, 99, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}