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: c4bd8ec87d7901b1a230969068dbdb263272d07641d6f467d317993bddd31adb
Tx prefix hash: e77d0cc9380af1d6a48f03717566ec660714ba9e7eea3123e1f63b16bcc7af14
Tx public key: b4e589ae614946d52175748a010e510ae49523c3ce850ee5a49f36cbc2c389c0
| Timestamp: 1779915984 | Timestamp [UTC]: 2026-05-27 21:06:24 | Age [y:d:h:m:s]: 00:012:04:29:33 |
| Block: 3300 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4586 | RingCT/type: yes/0 |
| Extra: 01b4e589ae614946d52175748a010e510ae49523c3ce850ee5a49f36cbc2c389c002090000000226697be300 | ||
1 output(s) for total of 34.963674815805 HMNY
| stealth address | amount | amount idx | tag |
| 00: 10dfcec6f7af35c09fe088676005dfaf2afe25d28f5e83222adf3c1d089112bd | 34.963674815805 | 3964 of 0 | <1b> |
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": 3360,
"vin": [ {
"gen": {
"height": 3300
}
}
],
"vout": [ {
"amount": 34963674815805,
"target": {
"tagged_key": {
"key": "10dfcec6f7af35c09fe088676005dfaf2afe25d28f5e83222adf3c1d089112bd",
"view_tag": "1b"
}
}
}
],
"extra": [ 1, 180, 229, 137, 174, 97, 73, 70, 213, 33, 117, 116, 138, 1, 14, 81, 10, 228, 149, 35, 195, 206, 133, 14, 229, 164, 159, 54, 203, 194, 195, 137, 192, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}