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: c93781de51ca1cdcc14e04f7fed3ba90df8699347688a150895633f553ddcfd5
Tx prefix hash: e8e52c1da37ab47f62746d2ad6d8d564f1e4e0df953b13dcd26aabbc7b1ba3ef
Tx public key: 7a1cac2a89559df22fc6cb69bb0e897ae16270da763ab151c5357a64c599216a
| Timestamp: 1780323043 | Timestamp [UTC]: 2026-06-01 14:10:43 | Age [y:d:h:m:s]: 00:007:10:36:04 |
| Block: 5045 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2841 | RingCT/type: yes/0 |
| Extra: 017a1cac2a89559df22fc6cb69bb0e897ae16270da763ab151c5357a64c599216a02090000000e26697be300 | ||
1 output(s) for total of 34.847497733916 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2cbeb0466f9b1da65c421bb9e843e0692b1f0a82279dbcef9eac0fdbe3a7c4c7 | 34.847497733916 | 6420 of 0 | <e6> |
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": 5105,
"vin": [ {
"gen": {
"height": 5045
}
}
],
"vout": [ {
"amount": 34847497733916,
"target": {
"tagged_key": {
"key": "2cbeb0466f9b1da65c421bb9e843e0692b1f0a82279dbcef9eac0fdbe3a7c4c7",
"view_tag": "e6"
}
}
}
],
"extra": [ 1, 122, 28, 172, 42, 137, 85, 157, 242, 47, 198, 203, 105, 187, 14, 137, 122, 225, 98, 112, 218, 118, 58, 177, 81, 197, 53, 122, 100, 197, 153, 33, 106, 2, 9, 0, 0, 0, 14, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}