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: edc9e7e15c61c54f955a79538b0ce220d269f21cf72eb21a50090ea1ee07f6a5
Tx prefix hash: d4e7aee806248c6783bb4f71e88d0d8c26a5c1d16330884ace0ab5d7066c9ab5
Tx public key: a1414594a30a16eb279616e5eea6831fdf84c9031f8263321d84d8f4e4e4b43e
| Timestamp: 1779791293 | Timestamp [UTC]: 2026-05-26 10:28:13 | Age [y:d:h:m:s]: 00:013:15:07:44 |
| Block: 2230 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5656 | RingCT/type: yes/0 |
| Extra: 01a1414594a30a16eb279616e5eea6831fdf84c9031f8263321d84d8f4e4e4b43e02090000000326697be300 | ||
1 output(s) for total of 35.044101419111 HMNY
| stealth address | amount | amount idx | tag |
| 00: 56c17701b86f5e52101f1e76356d4e4ff05a63e6763285e15dbc5a3835b7be38 | 35.044101419111 | 2582 of 0 | <0b> |
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": 2290,
"vin": [ {
"gen": {
"height": 2230
}
}
],
"vout": [ {
"amount": 35044101419111,
"target": {
"tagged_key": {
"key": "56c17701b86f5e52101f1e76356d4e4ff05a63e6763285e15dbc5a3835b7be38",
"view_tag": "0b"
}
}
}
],
"extra": [ 1, 161, 65, 69, 148, 163, 10, 22, 235, 39, 150, 22, 229, 238, 166, 131, 31, 223, 132, 201, 3, 31, 130, 99, 50, 29, 132, 216, 244, 228, 228, 180, 62, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}