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: 69afb00b6cacdebf9fb9ed7b52a7f7429c4b6f1ab08428d65e9f383de6723a11
Tx prefix hash: bad880df349f99f0bdbe5cd58d9ad66a15555d0c1eba33f5ca67465a75454b79
Tx public key: a441840822abccfefdd44c9bee1d3d55b0020658ee2c702cecdc7f979d3ad965
| Timestamp: 1780820870 | Timestamp [UTC]: 2026-06-07 08:27:50 | Age [y:d:h:m:s]: 00:001:18:12:46 |
| Block: 7166 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 731 | RingCT/type: yes/0 |
| Extra: 01a441840822abccfefdd44c9bee1d3d55b0020658ee2c702cecdc7f979d3ad965020900000001e49593ff00 | ||
1 output(s) for total of 34.706807292353 HMNY
| stealth address | amount | amount idx | tag |
| 00: 660feb4ce85e56fc6b2fa96c7341ed01effb0a610402ca4f4f01d43d9f68eaab | 34.706807292353 | 8828 of 0 | <f6> |
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": 7226,
"vin": [ {
"gen": {
"height": 7166
}
}
],
"vout": [ {
"amount": 34706807292353,
"target": {
"tagged_key": {
"key": "660feb4ce85e56fc6b2fa96c7341ed01effb0a610402ca4f4f01d43d9f68eaab",
"view_tag": "f6"
}
}
}
],
"extra": [ 1, 164, 65, 132, 8, 34, 171, 204, 254, 253, 212, 76, 155, 238, 29, 61, 85, 176, 2, 6, 88, 238, 44, 112, 44, 236, 220, 127, 151, 157, 58, 217, 101, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}