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: faf6edf2a10c6bdecfa5e92e6f95663327dace066b1834d27db65d0722980bdf
Tx prefix hash: 8868d2cf83623124526adb221b782d047598e443cfd19f48dfdfbd1184482cea
Tx public key: 4ad37f356df59be41066629638a3e1ff13abd1ed4e57efe79cbe6512bf08418d
| Timestamp: 1779642919 | Timestamp [UTC]: 2026-05-24 17:15:19 | Age [y:d:h:m:s]: 00:015:23:53:44 |
| Block: 1398 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7337 | RingCT/type: yes/0 |
| Extra: 014ad37f356df59be41066629638a3e1ff13abd1ed4e57efe79cbe6512bf08418d020900000001ba6d17be00 | ||
1 output(s) for total of 35.090745708879 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0069ba4fb4183e60d6f7a9f13c07340b15c385c096bdb35101d0120bc2d5b5b3 | 35.090745708879 | 1550 of 0 | <3f> |
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": 1458,
"vin": [ {
"gen": {
"height": 1398
}
}
],
"vout": [ {
"amount": 35090745708879,
"target": {
"tagged_key": {
"key": "0069ba4fb4183e60d6f7a9f13c07340b15c385c096bdb35101d0120bc2d5b5b3",
"view_tag": "3f"
}
}
}
],
"extra": [ 1, 74, 211, 127, 53, 109, 245, 155, 228, 16, 102, 98, 150, 56, 163, 225, 255, 19, 171, 209, 237, 78, 87, 239, 231, 156, 190, 101, 18, 191, 8, 65, 141, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}