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: 33c1bcd38d4c7ac2f3dd1c9f53484834538fc72222e8b31342a3b77600050f8c
Tx prefix hash: 6bb3b77ed4571c4bc4c311c42d38e854fa3d66a822d8067e9e610f408d1b182f
Tx public key: 4d5976ce72fe12f7c7cb9d9a675bb5008ed73060edc8a6fe82cef501e0c53d0c
| Timestamp: 1779883744 | Timestamp [UTC]: 2026-05-27 12:09:04 | Age [y:d:h:m:s]: 00:012:13:26:53 |
| Block: 2986 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4900 | RingCT/type: yes/0 |
| Extra: 014d5976ce72fe12f7c7cb9d9a675bb5008ed73060edc8a6fe82cef501e0c53d0c02090000000226697be300 | ||
1 output(s) for total of 34.984621113652 HMNY
| stealth address | amount | amount idx | tag |
| 00: c35269db52c4c962a8a61f09b459757151434cf5185e60f4d8521743026d0524 | 34.984621113652 | 3544 of 0 | <6f> |
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": 3046,
"vin": [ {
"gen": {
"height": 2986
}
}
],
"vout": [ {
"amount": 34984621113652,
"target": {
"tagged_key": {
"key": "c35269db52c4c962a8a61f09b459757151434cf5185e60f4d8521743026d0524",
"view_tag": "6f"
}
}
}
],
"extra": [ 1, 77, 89, 118, 206, 114, 254, 18, 247, 199, 203, 157, 154, 103, 91, 181, 0, 142, 215, 48, 96, 237, 200, 166, 254, 130, 206, 245, 1, 224, 197, 61, 12, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}