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: 89b430583474b7cd135db4dd56036eec11a00d26762a92b37f9230a918d8dd89
Tx prefix hash: fc79fd98580e87bb2248c19d5792d572e9b72368319c5fadef430fd795bddbe5
Tx public key: ec67a57b8e58faaa0ed6a241b21a8e83687f98886023ee848306d5156b7dd9d1
| Timestamp: 1779451418 | Timestamp [UTC]: 2026-05-22 12:03:38 | Age [y:d:h:m:s]: 00:017:13:32:19 |
| Block: 330 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7556 | RingCT/type: yes/0 |
| Extra: 01ec67a57b8e58faaa0ed6a241b21a8e83687f98886023ee848306d5156b7dd9d10209000000024438f87f00 | ||
1 output(s) for total of 35.162300177622 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5660e837eae5e80fa5bf5e2aaf018e5cbd9764a289d0efc4873a37a48f83528d | 35.162300177622 | 326 of 0 | <84> |
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": 390,
"vin": [ {
"gen": {
"height": 330
}
}
],
"vout": [ {
"amount": 35162300177622,
"target": {
"tagged_key": {
"key": "5660e837eae5e80fa5bf5e2aaf018e5cbd9764a289d0efc4873a37a48f83528d",
"view_tag": "84"
}
}
}
],
"extra": [ 1, 236, 103, 165, 123, 142, 88, 250, 170, 14, 214, 162, 65, 178, 26, 142, 131, 104, 127, 152, 136, 96, 35, 238, 132, 131, 6, 213, 21, 107, 125, 217, 209, 2, 9, 0, 0, 0, 2, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}