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: f6472aec183d08a372eae9749b01b3de6b64d91dd70ff2bc34b6183a1b3f2701
Tx prefix hash: 7ebab99e8031dd5210274b58ee44bef9f035461f604f0d3357f1d40502a5b23d
Tx public key: f51a2e39509136f9b8048fb9c49c0f9b43f5361a3f6d04498f346e8ca82cadcf
| Timestamp: 1780990599 | Timestamp [UTC]: 2026-06-09 07:36:39 | Age [y:d:h:m:s]: 00:000:08:53:08 |
| Block: 8225 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 491 | RingCT/type: yes/0 |
| Extra: 01f51a2e39509136f9b8048fb9c49c0f9b43f5361a3f6d04498f346e8ca82cadcf020900000001e49593ff00 | ||
1 output(s) for total of 34.636774316213 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3434c22cc5e206f3044c64b3f248ea473f350db3aeba5eed7ddfc4d90ba89a57 | 34.636774316213 | 10181 of 0 | <64> |
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": 8285,
"vin": [ {
"gen": {
"height": 8225
}
}
],
"vout": [ {
"amount": 34636774316213,
"target": {
"tagged_key": {
"key": "3434c22cc5e206f3044c64b3f248ea473f350db3aeba5eed7ddfc4d90ba89a57",
"view_tag": "64"
}
}
}
],
"extra": [ 1, 245, 26, 46, 57, 80, 145, 54, 249, 184, 4, 143, 185, 196, 156, 15, 155, 67, 245, 54, 26, 63, 109, 4, 73, 143, 52, 110, 140, 168, 44, 173, 207, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}