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: 9aa3450a479da95122f4713bea0235a9e04245f6469b00ae7f2ae61683716944
Tx prefix hash: 4e10ae15e3c0a103a52d36d933d28235407bba8e3ffd10912b24d9d814266359
Tx public key: 3f6170af82992baf9ccbbcdb606c470c8bf9a13ddac44ebd1f08bf1113f9a313
| Timestamp: 1779431779 | Timestamp [UTC]: 2026-05-22 06:36:19 | Age [y:d:h:m:s]: 00:017:15:48:30 |
| Block: 29 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0801 kB |
| Tx version: 2 | No of confirmations: 7857 | RingCT/type: yes/0 |
| Extra: 013f6170af82992baf9ccbbcdb606c470c8bf9a13ddac44ebd1f08bf1113f9a313 | ||
1 output(s) for total of 35.182493089136 HMNY
| stealth address | amount | amount idx | tag |
| 00: cf4063d46693226c9a103a104f895b7fb2a97246219cd33b09c71d37b9fb83ad | 35.182493089136 | 25 of 0 | <7a> |
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": 89,
"vin": [ {
"gen": {
"height": 29
}
}
],
"vout": [ {
"amount": 35182493089136,
"target": {
"tagged_key": {
"key": "cf4063d46693226c9a103a104f895b7fb2a97246219cd33b09c71d37b9fb83ad",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 63, 97, 112, 175, 130, 153, 43, 175, 156, 203, 188, 219, 96, 108, 71, 12, 139, 249, 161, 61, 218, 196, 78, 189, 31, 8, 191, 17, 19, 249, 163, 19
],
"rct_signatures": {
"type": 0
}
}