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: d8f2cb46fd2115c5577144a639ec4135d91e9696457490dcb1a14505c9aef19e
Tx prefix hash: 0c0e0887a0606ad379865d778cee3e4e311cc4c7209a5ed6194e947582b6e0c3
Tx public key: d760e8709165e72f77d31d9607466bf7d91066a1f79ac9a765a4388fedebff81
| Timestamp: 1779854248 | Timestamp [UTC]: 2026-05-27 03:57:28 | Age [y:d:h:m:s]: 00:012:21:38:29 |
| Block: 2592 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5294 | RingCT/type: yes/0 |
| Extra: 01d760e8709165e72f77d31d9607466bf7d91066a1f79ac9a765a4388fedebff8102090000000126697be300 | ||
1 output(s) for total of 35.010921800403 HMNY
| stealth address | amount | amount idx | tag |
| 00: 145b14e56addd4a651f93ae8e41036340c89777deed9b4522cfceb2c7f8b663c | 35.010921800403 | 3050 of 0 | <27> |
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": 2652,
"vin": [ {
"gen": {
"height": 2592
}
}
],
"vout": [ {
"amount": 35010921800403,
"target": {
"tagged_key": {
"key": "145b14e56addd4a651f93ae8e41036340c89777deed9b4522cfceb2c7f8b663c",
"view_tag": "27"
}
}
}
],
"extra": [ 1, 215, 96, 232, 112, 145, 101, 231, 47, 119, 211, 29, 150, 7, 70, 107, 247, 217, 16, 102, 161, 247, 154, 201, 167, 101, 164, 56, 143, 237, 235, 255, 129, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}