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: 8d94b2486d44f9976f39dbdc8a158868b9e775feb29e0495df12a9f5f3888dfa
Tx prefix hash: 51922cd7d8f4f17de7a1e62d9d040ee4909dc2221a64834e56d328b06915484d
Tx public key: 3c109764c4168bbc964e4676f5f1df62b9d0cc3ab9f23c4721cd41a707db26f4
| Timestamp: 1779712346 | Timestamp [UTC]: 2026-05-25 12:32:26 | Age [y:d:h:m:s]: 00:014:13:03:31 |
| Block: 1587 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6299 | RingCT/type: yes/0 |
| Extra: 013c109764c4168bbc964e4676f5f1df62b9d0cc3ab9f23c4721cd41a707db26f4020900000002ba6d17be00 | ||
1 output(s) for total of 35.078098152580 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5870caa20673c71e7129e8121cba47112b6a948223d7ad8d7180fa3fe21963fc | 35.078098152580 | 1745 of 0 | <0a> |
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": 1647,
"vin": [ {
"gen": {
"height": 1587
}
}
],
"vout": [ {
"amount": 35078098152580,
"target": {
"tagged_key": {
"key": "5870caa20673c71e7129e8121cba47112b6a948223d7ad8d7180fa3fe21963fc",
"view_tag": "0a"
}
}
}
],
"extra": [ 1, 60, 16, 151, 100, 196, 22, 139, 188, 150, 78, 70, 118, 245, 241, 223, 98, 185, 208, 204, 58, 185, 242, 60, 71, 33, 205, 65, 167, 7, 219, 38, 244, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}