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: faf28a1e276cb7e8d1af5619b6fd34dcb51d4d91082bede8481ddc09988e8203
Tx prefix hash: fa0661d4298f6c9ca90c7d3f98c85f1f0953762311237aa4560233f741708f91
Tx public key: 861e6ce018a7958b7b53dd961efdf64397936e020f1f60a656c3a698050a12dd
| Timestamp: 1780991506 | Timestamp [UTC]: 2026-06-09 07:51:46 | Age [y:d:h:m:s]: 00:000:04:45:59 |
| Block: 8240 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 336 | RingCT/type: yes/0 |
| Extra: 01861e6ce018a7958b7b53dd961efdf64397936e020f1f60a656c3a698050a12dd020900000002e49593ff00 | ||
1 output(s) for total of 34.635783363381 HMNY
| stealth address | amount | amount idx | tag |
| 00: d05c586d59714b83117866d6171582c90ed16a81dd5b0d2adddea1260c402f27 | 34.635783363381 | 10200 of 0 | <c5> |
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": 8300,
"vin": [ {
"gen": {
"height": 8240
}
}
],
"vout": [ {
"amount": 34635783363381,
"target": {
"tagged_key": {
"key": "d05c586d59714b83117866d6171582c90ed16a81dd5b0d2adddea1260c402f27",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 134, 30, 108, 224, 24, 167, 149, 139, 123, 83, 221, 150, 30, 253, 246, 67, 151, 147, 110, 2, 15, 31, 96, 166, 86, 195, 166, 152, 5, 10, 18, 221, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}