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: 75a720c364e5ebdf1ff5ed9fa823f5c379f3bb746cc3e2fac26877b83945b705
Tx prefix hash: a63de1ac770b43eb47ddf845ec45b0e6c6c017464f11ed3519a84273cfb7e1de
Tx public key: 2569e6068088a8862d27f5243974a1cfbe0342d094442fb7d8ffc286f1efc2bc
| Timestamp: 1779862816 | Timestamp [UTC]: 2026-05-27 06:20:16 | Age [y:d:h:m:s]: 00:012:18:26:31 |
| Block: 2703 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5183 | RingCT/type: yes/0 |
| Extra: 012569e6068088a8862d27f5243974a1cfbe0342d094442fb7d8ffc286f1efc2bc02090000000126697be300 | ||
1 output(s) for total of 35.010107816182 HMNY
| stealth address | amount | amount idx | tag |
| 00: c09c4cc0ce1dc3ca09c59bbf0aff95c64649e7306a76cf5c6c9718e416fda777 | 35.010107816182 | 3189 of 0 | <82> |
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": 2763,
"vin": [ {
"gen": {
"height": 2703
}
}
],
"vout": [ {
"amount": 35010107816182,
"target": {
"tagged_key": {
"key": "c09c4cc0ce1dc3ca09c59bbf0aff95c64649e7306a76cf5c6c9718e416fda777",
"view_tag": "82"
}
}
}
],
"extra": [ 1, 37, 105, 230, 6, 128, 136, 168, 134, 45, 39, 245, 36, 57, 116, 161, 207, 190, 3, 66, 208, 148, 68, 47, 183, 216, 255, 194, 134, 241, 239, 194, 188, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}