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: b16268e7fe400394739ed751d7de4dea9daac6f07cd6fbd8d498211c001acf18
Tx prefix hash: b842b9de9e5b8228417b39f35144e357eb50549ce286f5323537e119aa1ad3fa
Tx public key: eda1c151843a6eb9a02a8ae53a80b3731e4f72f83cf0ef97b5623fbf8c73f1fa
| Timestamp: 1779724530 | Timestamp [UTC]: 2026-05-25 15:55:30 | Age [y:d:h:m:s]: 00:014:09:40:27 |
| Block: 1825 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6061 | RingCT/type: yes/0 |
| Extra: 01eda1c151843a6eb9a02a8ae53a80b3731e4f72f83cf0ef97b5623fbf8c73f1fa020900000001ba6d17be00 | ||
1 output(s) for total of 35.062178084433 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2b32064f47e6d97f6f3709951d76b0fb01f6647aaeaee40a56fac5adc3052369 | 35.062178084433 | 2019 of 0 | <ad> |
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": 1885,
"vin": [ {
"gen": {
"height": 1825
}
}
],
"vout": [ {
"amount": 35062178084433,
"target": {
"tagged_key": {
"key": "2b32064f47e6d97f6f3709951d76b0fb01f6647aaeaee40a56fac5adc3052369",
"view_tag": "ad"
}
}
}
],
"extra": [ 1, 237, 161, 193, 81, 132, 58, 110, 185, 160, 42, 138, 229, 58, 128, 179, 115, 30, 79, 114, 248, 60, 240, 239, 151, 181, 98, 63, 191, 140, 115, 241, 250, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}