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: b1280ec758ce1149c34b83b8318c9b6d8b986c7a400fb74c4d010dc0c4788253
Tx prefix hash: 50124c1fafe929badd7ff6a97dedc395b2b2b188f7cf62bac22f8bede88db984
Tx public key: 902f43c5a3a4324e0cfaed4e30332c4e758f99ca49e72137a0b804d6b207860d
| Timestamp: 1780690047 | Timestamp [UTC]: 2026-06-05 20:07:27 | Age [y:d:h:m:s]: 00:003:06:42:21 |
| Block: 5631 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2278 | RingCT/type: yes/0 |
| Extra: 01902f43c5a3a4324e0cfaed4e30332c4e758f99ca49e72137a0b804d6b207860d020900000001e49593ff00 | ||
1 output(s) for total of 34.808570187911 HMNY
| stealth address | amount | amount idx | tag |
| 00: f02517a37fcafe7092ff3af589401178d856b834800137278040444c51dd2355 | 34.808570187911 | 7078 of 0 | <66> |
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": 5691,
"vin": [ {
"gen": {
"height": 5631
}
}
],
"vout": [ {
"amount": 34808570187911,
"target": {
"tagged_key": {
"key": "f02517a37fcafe7092ff3af589401178d856b834800137278040444c51dd2355",
"view_tag": "66"
}
}
}
],
"extra": [ 1, 144, 47, 67, 197, 163, 164, 50, 78, 12, 250, 237, 78, 48, 51, 44, 78, 117, 143, 153, 202, 73, 231, 33, 55, 160, 184, 4, 214, 178, 7, 134, 13, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}