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: 76d7dd9156568581ec672ec4e052a836a73b1076127761365702c7bd43a588f1
Tx prefix hash: 7b7d75eb510c968831d42766d2ba8e1c367fd9ea8cf57c292444d57fad28b134
Tx public key: d9763a7793f1463d8a3676b114fecdcc084c29b00aa4393c3970ddb47be1d6d5
| Timestamp: 1779955819 | Timestamp [UTC]: 2026-05-28 08:10:19 | Age [y:d:h:m:s]: 00:011:18:30:17 |
| Block: 3689 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4208 | RingCT/type: yes/0 |
| Extra: 01d9763a7793f1463d8a3676b114fecdcc084c29b00aa4393c3970ddb47be1d6d502090000000226697be300 | ||
1 output(s) for total of 34.937742812648 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0305fd501e6c85d03719febccb5bbc57ab436cdc0724270c1088bdf8ac9328db | 34.937742812648 | 4462 of 0 | <7a> |
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": 3749,
"vin": [ {
"gen": {
"height": 3689
}
}
],
"vout": [ {
"amount": 34937742812648,
"target": {
"tagged_key": {
"key": "0305fd501e6c85d03719febccb5bbc57ab436cdc0724270c1088bdf8ac9328db",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 217, 118, 58, 119, 147, 241, 70, 61, 138, 54, 118, 177, 20, 254, 205, 204, 8, 76, 41, 176, 10, 164, 57, 60, 57, 112, 221, 180, 123, 225, 214, 213, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}