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: 71cf0db9670b4605d504590a7fc9c3f0e20caaa1a4003e1f09371f043c67345c
Tx prefix hash: 30939b40ef794e5e780beb4e09daf6fc2c3466911fe78c456873fbfd81084be6
Tx public key: 076425779c2ce3a8ea3dd0a4bcdb54c14393a9e96c696059359b0edf49441801
| Timestamp: 1780974489 | Timestamp [UTC]: 2026-06-09 03:08:09 | Age [y:d:h:m:s]: 00:000:10:29:27 |
| Block: 7919 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 691 | RingCT/type: yes/0 |
| Extra: 01076425779c2ce3a8ea3dd0a4bcdb54c14393a9e96c696059359b0edf49441801020900000002e49593ff00 | ||
1 output(s) for total of 34.656995943753 HMNY
| stealth address | amount | amount idx | tag |
| 00: be65ad7c15eece26f2795c44dee97d437ea8de5101b5c5d4016cf2be9a5954f6 | 34.656995943753 | 9819 of 0 | <68> |
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": 7979,
"vin": [ {
"gen": {
"height": 7919
}
}
],
"vout": [ {
"amount": 34656995943753,
"target": {
"tagged_key": {
"key": "be65ad7c15eece26f2795c44dee97d437ea8de5101b5c5d4016cf2be9a5954f6",
"view_tag": "68"
}
}
}
],
"extra": [ 1, 7, 100, 37, 119, 156, 44, 227, 168, 234, 61, 208, 164, 188, 219, 84, 193, 67, 147, 169, 233, 108, 105, 96, 89, 53, 155, 14, 223, 73, 68, 24, 1, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}