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: 43692bd8e9eabc63932cefff3acb62721fc3d586282862a92a12df3ffb94e638
Tx prefix hash: b5231f4ac762bb6d0d4bfa01c49e17401b206181d619e5918121d18f62255057
Tx public key: 66718806c638343e91282bc96febe05f55a73e744e0f3a7f8f440bc6f215e5f4
| Timestamp: 1780859470 | Timestamp [UTC]: 2026-06-07 19:11:10 | Age [y:d:h:m:s]: 00:001:05:35:37 |
| Block: 7605 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 281 | RingCT/type: yes/0 |
| Extra: 0166718806c638343e91282bc96febe05f55a73e744e0f3a7f8f440bc6f215e5f4020900000001e49593ff00 | ||
1 output(s) for total of 34.677758514145 HMNY
| stealth address | amount | amount idx | tag |
| 00: 194aca67bd050e2a0f9d0db29234cd633d30fbcd35325bb52b88b45fb5aecad6 | 34.677758514145 | 9397 of 0 | <d3> |
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": 7665,
"vin": [ {
"gen": {
"height": 7605
}
}
],
"vout": [ {
"amount": 34677758514145,
"target": {
"tagged_key": {
"key": "194aca67bd050e2a0f9d0db29234cd633d30fbcd35325bb52b88b45fb5aecad6",
"view_tag": "d3"
}
}
}
],
"extra": [ 1, 102, 113, 136, 6, 198, 56, 52, 62, 145, 40, 43, 201, 111, 235, 224, 95, 85, 167, 62, 116, 78, 15, 58, 127, 143, 68, 11, 198, 242, 21, 229, 244, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}