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: 930cffeb9614ebdc7d392efcdd0cca4b268a54df0ec956430826f329b6f7131e
Tx prefix hash: 8f0dfe53d69b447bfda432734dea25e2d1ba44e4c94e0bec18f6cf1564a45a19
Tx public key: 16acd632fdad163087b2acb824fc1a75dd5621a5d6c95c74e4e487be43d07d56
| Timestamp: 1779715906 | Timestamp [UTC]: 2026-05-25 13:31:46 | Age [y:d:h:m:s]: 00:022:18:57:26 |
| Block: 1640 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7105 | RingCT/type: yes/0 |
| Extra: 0116acd632fdad163087b2acb824fc1a75dd5621a5d6c95c74e4e487be43d07d56020900000001ba6d17be00 | ||
1 output(s) for total of 35.074552301810 HMNY
| stealth address | amount | amount idx | tag |
| 00: 173af16464844aae0bdf1b72ce01c2eb9aeb25eeaa40b7909a036097213fb4bf | 35.074552301810 | 1802 of 0 | <aa> |
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": 1700,
"vin": [ {
"gen": {
"height": 1640
}
}
],
"vout": [ {
"amount": 35074552301810,
"target": {
"tagged_key": {
"key": "173af16464844aae0bdf1b72ce01c2eb9aeb25eeaa40b7909a036097213fb4bf",
"view_tag": "aa"
}
}
}
],
"extra": [ 1, 22, 172, 214, 50, 253, 173, 22, 48, 135, 178, 172, 184, 36, 252, 26, 117, 221, 86, 33, 165, 214, 201, 92, 116, 228, 228, 135, 190, 67, 208, 125, 86, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}