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: bb8a3016a275eb5349baef5f9e613cf1660a25183d9f86563e0ff267e64671df
Tx prefix hash: 4a7692c344702169a635a4660bd5f46fa5a6654a8e57dc4de422f5281c436839
Tx public key: 99138d1802c693fe3a7d50caa5c336f75ca974f2d971d299ae79bea4c508a067
| Timestamp: 1779633664 | Timestamp [UTC]: 2026-05-24 14:41:04 | Age [y:d:h:m:s]: 00:015:13:51:58 |
| Block: 1000 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7026 | RingCT/type: yes/0 |
| Extra: 0199138d1802c693fe3a7d50caa5c336f75ca974f2d971d299ae79bea4c508a067020900000001ba6d17be00 | ||
1 output(s) for total of 35.117394101510 HMNY
| stealth address | amount | amount idx | tag |
| 00: e2089a59ec8e4ec198272fd5e8fd55ef4a6fb77762b734e6ba183728c91675d5 | 35.117394101510 | 1136 of 0 | <ec> |
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": 1060,
"vin": [ {
"gen": {
"height": 1000
}
}
],
"vout": [ {
"amount": 35117394101510,
"target": {
"tagged_key": {
"key": "e2089a59ec8e4ec198272fd5e8fd55ef4a6fb77762b734e6ba183728c91675d5",
"view_tag": "ec"
}
}
}
],
"extra": [ 1, 153, 19, 141, 24, 2, 198, 147, 254, 58, 125, 80, 202, 165, 195, 54, 247, 92, 169, 116, 242, 217, 113, 210, 153, 174, 121, 190, 164, 197, 8, 160, 103, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}