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: d66bacde67e54f07b42669a4cdbc4ebf570692cbe4528b4f36b645c9f467121c
Tx prefix hash: 7e4daf522b159335a4f3874c549d47d5eac0e705e8f3698d46de754f620f4cad
Tx public key: 0eec4b5e5dcc0190c38b98621f38b8919c7a63c00cb25824fc4769a07f0acdf8
| Timestamp: 1780843089 | Timestamp [UTC]: 2026-06-07 14:38:09 | Age [y:d:h:m:s]: 00:001:10:08:38 |
| Block: 7482 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 404 | RingCT/type: yes/0 |
| Extra: 010eec4b5e5dcc0190c38b98621f38b8919c7a63c00cb25824fc4769a07f0acdf8020900000002e49593ff00 | ||
1 output(s) for total of 34.685895013055 HMNY
| stealth address | amount | amount idx | tag |
| 00: 385b3069b440730d519f27c0179c868d8a0d17cc0d984126398f9ada665d6ab3 | 34.685895013055 | 9218 of 0 | <fe> |
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": 7542,
"vin": [ {
"gen": {
"height": 7482
}
}
],
"vout": [ {
"amount": 34685895013055,
"target": {
"tagged_key": {
"key": "385b3069b440730d519f27c0179c868d8a0d17cc0d984126398f9ada665d6ab3",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 14, 236, 75, 94, 93, 204, 1, 144, 195, 139, 152, 98, 31, 56, 184, 145, 156, 122, 99, 192, 12, 178, 88, 36, 252, 71, 105, 160, 127, 10, 205, 248, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}