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: f134c5faece6205ff4fce174f0829a6d01e67b6e992ef4096afdda3d91c50eea
Tx prefix hash: 82156dd37ff0c77116b2fce4b5484a36eb96478523ad787f5faa9bf60738caee
Tx public key: 938aca6d9e7c0e643622d8109773d387ea10211fe430cd0ff0c7fc8153465fd2
| Timestamp: 1779847014 | Timestamp [UTC]: 2026-05-27 01:56:54 | Age [y:d:h:m:s]: 00:021:06:08:27 |
| Block: 2472 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6273 | RingCT/type: yes/0 |
| Extra: 01938aca6d9e7c0e643622d8109773d387ea10211fe430cd0ff0c7fc8153465fd202090000000126697be300 | ||
1 output(s) for total of 35.018936089233 HMNY
| stealth address | amount | amount idx | tag |
| 00: 30611c24fff020b6d0e251ec1b511c931ef2c24536587692d7cded9b32d7474f | 35.018936089233 | 2906 of 0 | <2f> |
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": 2532,
"vin": [ {
"gen": {
"height": 2472
}
}
],
"vout": [ {
"amount": 35018936089233,
"target": {
"tagged_key": {
"key": "30611c24fff020b6d0e251ec1b511c931ef2c24536587692d7cded9b32d7474f",
"view_tag": "2f"
}
}
}
],
"extra": [ 1, 147, 138, 202, 109, 158, 124, 14, 100, 54, 34, 216, 16, 151, 115, 211, 135, 234, 16, 33, 31, 228, 48, 205, 15, 240, 199, 252, 129, 83, 70, 95, 210, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}