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: e8492c6f2affe0cd98189ae56fc062ed11ebecc6edf51cafbf82c866798c027a
Tx prefix hash: 0add4d62cc4bb3e9123742486b4c88ce4e3fee7576828357dfc0006d24a086cf
Tx public key: 7e8d6d9c22212168332abc829768b3dc6b60f1f81a509ba9d909d34fb8136b1a
| Timestamp: 1780323263 | Timestamp [UTC]: 2026-06-01 14:14:23 | Age [y:d:h:m:s]: 00:011:20:47:53 |
| Block: 5092 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3653 | RingCT/type: yes/0 |
| Extra: 017e8d6d9c22212168332abc829768b3dc6b60f1f81a509ba9d909d34fb8136b1a02090000000426697be300 | ||
1 output(s) for total of 34.844373953579 HMNY
| stealth address | amount | amount idx | tag |
| 00: e439d642ac36f0603bc5240d2e7fd107a62299b1e2b0ebdc0ee2e1edc39d3b09 | 34.844373953579 | 6467 of 0 | <0d> |
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": 5152,
"vin": [ {
"gen": {
"height": 5092
}
}
],
"vout": [ {
"amount": 34844373953579,
"target": {
"tagged_key": {
"key": "e439d642ac36f0603bc5240d2e7fd107a62299b1e2b0ebdc0ee2e1edc39d3b09",
"view_tag": "0d"
}
}
}
],
"extra": [ 1, 126, 141, 109, 156, 34, 33, 33, 104, 51, 42, 188, 130, 151, 104, 179, 220, 107, 96, 241, 248, 26, 80, 155, 169, 217, 9, 211, 79, 184, 19, 107, 26, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}