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: bbd3095aab45d4934afdbcb30090c4c73eb73c7edef52a12150d3658132a3382
Tx prefix hash: 95bfaa60479b6519913df7a67032ddd72e7bd20a4acb5df0e52c4a65700c922e
Tx public key: 8a5a361c1ce044497cdeeba2f6dcacd4aab0e994aa904f3689608eb0516cd305
| Timestamp: 1780026103 | Timestamp [UTC]: 2026-05-29 03:41:43 | Age [y:d:h:m:s]: 00:010:21:05:04 |
| Block: 4170 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3716 | RingCT/type: yes/0 |
| Extra: 018a5a361c1ce044497cdeeba2f6dcacd4aab0e994aa904f3689608eb0516cd30502090000000326697be300 | ||
1 output(s) for total of 34.905704383594 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4e4364cea6df2d0c20c2f0e9b8b56d27a0184e0e34ff246fb2a233ef21ed7a9f | 34.905704383594 | 5203 of 0 | <dd> |
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": 4230,
"vin": [ {
"gen": {
"height": 4170
}
}
],
"vout": [ {
"amount": 34905704383594,
"target": {
"tagged_key": {
"key": "4e4364cea6df2d0c20c2f0e9b8b56d27a0184e0e34ff246fb2a233ef21ed7a9f",
"view_tag": "dd"
}
}
}
],
"extra": [ 1, 138, 90, 54, 28, 28, 224, 68, 73, 124, 222, 235, 162, 246, 220, 172, 212, 170, 176, 233, 148, 170, 144, 79, 54, 137, 96, 142, 176, 81, 108, 211, 5, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}