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: 08abd0ad0a3b2704447315f2a70ba961ce4089333bccf0da1d92bb34de4a1364
Tx prefix hash: d0092b3dcab1ec18c8acadca21b1dd37564112f7f5c7d1101026905c58469f50
Tx public key: 65911d42e23811fbf45e11e9b3e05d846d766e035ff63f1eb855fba9e925396c
| Timestamp: 1779630053 | Timestamp [UTC]: 2026-05-24 13:40:53 | Age [y:d:h:m:s]: 00:015:13:08:55 |
| Block: 857 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7063 | RingCT/type: yes/0 |
| Extra: 0165911d42e23811fbf45e11e9b3e05d846d766e035ff63f1eb855fba9e925396c020900000001ba6d17be00 | ||
1 output(s) for total of 35.126973716259 HMNY
| stealth address | amount | amount idx | tag |
| 00: fc6fac1181f70c45c4f4d57fd20844cd963a93f4c626a52e9ebd98bdcdaaef3f | 35.126973716259 | 989 of 0 | <6b> |
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": 917,
"vin": [ {
"gen": {
"height": 857
}
}
],
"vout": [ {
"amount": 35126973716259,
"target": {
"tagged_key": {
"key": "fc6fac1181f70c45c4f4d57fd20844cd963a93f4c626a52e9ebd98bdcdaaef3f",
"view_tag": "6b"
}
}
}
],
"extra": [ 1, 101, 145, 29, 66, 226, 56, 17, 251, 244, 94, 17, 233, 179, 224, 93, 132, 109, 118, 110, 3, 95, 246, 63, 30, 184, 85, 251, 169, 233, 37, 57, 108, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}