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: 03083864a72e48b1b6f92c6a3f22f729b3923540c3ae7d6988e3bc5288b5dcd0
Tx prefix hash: 6a0540f2063ebb034e227d6c07371c10c141aca923554f31f38866cb5a26cc59
Tx public key: d73f3501cd94d59782fa3048c0919fa02e96125de3645d389384a72a7e7160ca
| Timestamp: 1779443674 | Timestamp [UTC]: 2026-05-22 09:54:34 | Age [y:d:h:m:s]: 00:017:15:41:23 |
| Block: 242 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7644 | RingCT/type: yes/0 |
| Extra: 01d73f3501cd94d59782fa3048c0919fa02e96125de3645d389384a72a7e7160ca0209000000044438f87f00 | ||
1 output(s) for total of 35.168202553919 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8b46c4d4d0c153f1d79c18dbce62243312c88733ea611360a8830206ff644d16 | 35.168202553919 | 238 of 0 | <a1> |
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": 302,
"vin": [ {
"gen": {
"height": 242
}
}
],
"vout": [ {
"amount": 35168202553919,
"target": {
"tagged_key": {
"key": "8b46c4d4d0c153f1d79c18dbce62243312c88733ea611360a8830206ff644d16",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 215, 63, 53, 1, 205, 148, 213, 151, 130, 250, 48, 72, 192, 145, 159, 160, 46, 150, 18, 93, 227, 100, 93, 56, 147, 132, 167, 42, 126, 113, 96, 202, 2, 9, 0, 0, 0, 4, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}