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: 83e14cadf91bad755799b1e12b71f6e904c10a9b6a97b79c77a8a18dd642d32c
Tx prefix hash: dacbec047c6b95abe462309c1ed2fcec1396c341efc5edab44917359ca17bf63
Tx public key: 053ef639c8b0a731a4a0663358e3d549f828311e27ac905d22fb8c852d12f0ac
| Timestamp: 1780973479 | Timestamp [UTC]: 2026-06-09 02:51:19 | Age [y:d:h:m:s]: 00:000:11:12:39 |
| Block: 7901 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 709 | RingCT/type: yes/0 |
| Extra: 01053ef639c8b0a731a4a0663358e3d549f828311e27ac905d22fb8c852d12f0ac020900000001e49593ff00 | ||
1 output(s) for total of 34.658185818842 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4fc58db19248d234fb19ba8d1eaaa1cec65377013d51052307b973a293f384f8 | 34.658185818842 | 9799 of 0 | <af> |
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": 7961,
"vin": [ {
"gen": {
"height": 7901
}
}
],
"vout": [ {
"amount": 34658185818842,
"target": {
"tagged_key": {
"key": "4fc58db19248d234fb19ba8d1eaaa1cec65377013d51052307b973a293f384f8",
"view_tag": "af"
}
}
}
],
"extra": [ 1, 5, 62, 246, 57, 200, 176, 167, 49, 164, 160, 102, 51, 88, 227, 213, 73, 248, 40, 49, 30, 39, 172, 144, 93, 34, 251, 140, 133, 45, 18, 240, 172, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}