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: 76492003d65850a0e623b9291c35514e00d11964ee7129009c864c1ff4e47743
Tx prefix hash: ae6f7284d0de4ce30d97777ddba6c22c278901d879a9820e1e053f26ba0390c4
Tx public key: 54e33dc09fac42f34aae9cef35165ab1a4807a6a63bd859883fd7cde5d8ee393
| Timestamp: 1779638712 | Timestamp [UTC]: 2026-05-24 16:05:12 | Age [y:d:h:m:s]: 00:015:09:30:45 |
| Block: 1210 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6676 | RingCT/type: yes/0 |
| Extra: 0154e33dc09fac42f34aae9cef35165ab1a4807a6a63bd859883fd7cde5d8ee393020900000001ba6d17be00 | ||
1 output(s) for total of 35.103330870890 HMNY
| stealth address | amount | amount idx | tag |
| 00: a878565c647faf9a51c0b6a14243b95946e31b058c052a0cf420c0c165740fc3 | 35.103330870890 | 1354 of 0 | <2b> |
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": 1270,
"vin": [ {
"gen": {
"height": 1210
}
}
],
"vout": [ {
"amount": 35103330870890,
"target": {
"tagged_key": {
"key": "a878565c647faf9a51c0b6a14243b95946e31b058c052a0cf420c0c165740fc3",
"view_tag": "2b"
}
}
}
],
"extra": [ 1, 84, 227, 61, 192, 159, 172, 66, 243, 74, 174, 156, 239, 53, 22, 90, 177, 164, 128, 122, 106, 99, 189, 133, 152, 131, 253, 124, 222, 93, 142, 227, 147, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}