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: c4c42323b77d5ae0612deb068158a85095f16de75b98311b8fc3f3bcbc08fa1d
Tx prefix hash: c4ec6dfc08036e66d5933c3c6a46e6c5a9c6c35ff321a3080de74364a60a5d85
Tx public key: 089aaa561f43e26bd48d70b1fb6ad4677cec83c4aa95df19a036728dec42a7f3
| Timestamp: 1779774396 | Timestamp [UTC]: 2026-05-26 05:46:36 | Age [y:d:h:m:s]: 00:013:19:00:11 |
| Block: 2054 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5832 | RingCT/type: yes/0 |
| Extra: 01089aaa561f43e26bd48d70b1fb6ad4677cec83c4aa95df19a036728dec42a7f302090000000126697be300 | ||
1 output(s) for total of 35.046866856303 HMNY
| stealth address | amount | amount idx | tag |
| 00: 75242221c982779cb47b82c096590dfafdd0fd99521d0a4b7ebe83056726e84d | 35.046866856303 | 2350 of 0 | <59> |
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": 2114,
"vin": [ {
"gen": {
"height": 2054
}
}
],
"vout": [ {
"amount": 35046866856303,
"target": {
"tagged_key": {
"key": "75242221c982779cb47b82c096590dfafdd0fd99521d0a4b7ebe83056726e84d",
"view_tag": "59"
}
}
}
],
"extra": [ 1, 8, 154, 170, 86, 31, 67, 226, 107, 212, 141, 112, 177, 251, 106, 212, 103, 124, 236, 131, 196, 170, 149, 223, 25, 160, 54, 114, 141, 236, 66, 167, 243, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}