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: f5efd214bc9eaebba4a891f77ed3b94abf609ec4b319acb15d39e48efc52a0d1
Tx prefix hash: f818ccf69758c4a313c844c24eb77c0728fb345d638fd3e9f3c08ee037ba7db0
Tx public key: faaf86a45a2aed2f482688aaf0d703f486c0d1055c8a0ea82a84a5ffaed3cffc
| Timestamp: 1780833789 | Timestamp [UTC]: 2026-06-07 12:03:09 | Age [y:d:h:m:s]: 00:001:13:32:48 |
| Block: 7375 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 511 | RingCT/type: yes/0 |
| Extra: 01faaf86a45a2aed2f482688aaf0d703f486c0d1055c8a0ea82a84a5ffaed3cffc020900000001e49593ff00 | ||
1 output(s) for total of 34.692974658316 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9261c23b0236277bb4977f55172b5432b6eddd77ba59ec06b145abd9076cf5d9 | 34.692974658316 | 9081 of 0 | <90> |
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": 7435,
"vin": [ {
"gen": {
"height": 7375
}
}
],
"vout": [ {
"amount": 34692974658316,
"target": {
"tagged_key": {
"key": "9261c23b0236277bb4977f55172b5432b6eddd77ba59ec06b145abd9076cf5d9",
"view_tag": "90"
}
}
}
],
"extra": [ 1, 250, 175, 134, 164, 90, 42, 237, 47, 72, 38, 136, 170, 240, 215, 3, 244, 134, 192, 209, 5, 92, 138, 14, 168, 42, 132, 165, 255, 174, 211, 207, 252, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}