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: 4a8035517e7fa8a3f95838eb1439180c40c34a07af3d55d131c8e350506e1e7c
Tx prefix hash: f73f8560be7876f49bc2456808997321ffd4584afcedd3d49b9145939797b9ef
Tx public key: d92ca6d4e1a41ce60aaecfcaa17e25381ef43bc41b0bc55ca5f6eae5ff004b84
| Timestamp: 1779624028 | Timestamp [UTC]: 2026-05-24 12:00:28 | Age [y:d:h:m:s]: 00:015:13:35:29 |
| Block: 770 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 7116 | RingCT/type: yes/0 |
| Extra: 01d92ca6d4e1a41ce60aaecfcaa17e25381ef43bc41b0bc55ca5f6eae5ff004b84 | ||
1 output(s) for total of 35.132803151992 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0a99676f2f873a3a66aa9b55189df48259c957eccbb46e4dd1e697dfeb946e0a | 35.132803151992 | 902 of 0 | <73> |
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": 830,
"vin": [ {
"gen": {
"height": 770
}
}
],
"vout": [ {
"amount": 35132803151992,
"target": {
"tagged_key": {
"key": "0a99676f2f873a3a66aa9b55189df48259c957eccbb46e4dd1e697dfeb946e0a",
"view_tag": "73"
}
}
}
],
"extra": [ 1, 217, 44, 166, 212, 225, 164, 28, 230, 10, 174, 207, 202, 161, 126, 37, 56, 30, 244, 59, 196, 27, 11, 197, 92, 165, 246, 234, 229, 255, 0, 75, 132
],
"rct_signatures": {
"type": 0
}
}