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: 20871e52fee2f67b16a6420f8864fd155a0200742ca236d4e772fe11945d114c
Tx prefix hash: 08e3f0fcaa5df6bad206f77382fd10c75c00a95f5b44fbb0700fb129bb672d36
Tx public key: eebd19b7b778af30164425e92a810bcb4c29fea8f1f1a4ee406d832b779543c6
| Timestamp: 1779862259 | Timestamp [UTC]: 2026-05-27 06:10:59 | Age [y:d:h:m:s]: 00:012:19:24:58 |
| Block: 2698 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5188 | RingCT/type: yes/0 |
| Extra: 01eebd19b7b778af30164425e92a810bcb4c29fea8f1f1a4ee406d832b779543c602090000000126697be300 | ||
1 output(s) for total of 35.003844037579 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4d1460025fe57819cfc8c1fe6ff0fd76c0c7810d7db754f5332a629f9acd3a7a | 35.003844037579 | 3184 of 0 | <e1> |
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": 2758,
"vin": [ {
"gen": {
"height": 2698
}
}
],
"vout": [ {
"amount": 35003844037579,
"target": {
"tagged_key": {
"key": "4d1460025fe57819cfc8c1fe6ff0fd76c0c7810d7db754f5332a629f9acd3a7a",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 238, 189, 25, 183, 183, 120, 175, 48, 22, 68, 37, 233, 42, 129, 11, 203, 76, 41, 254, 168, 241, 241, 164, 238, 64, 109, 131, 43, 119, 149, 67, 198, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}