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: 8a66ed890b47c5aa10ecb148c376d8ca7433ae53e6e3ec78e6fdabea612e2b47
Tx prefix hash: 2c80769f9c52922ea7331c0a0fce628aabbfa302dfe716c02e0719e89d47f641
Tx public key: f9895bd40bc15b845602c744189e2f5d1ba6ccc132a25a692ecbc35365b6bcee
| Timestamp: 1779948020 | Timestamp [UTC]: 2026-05-28 06:00:20 | Age [y:d:h:m:s]: 00:011:15:11:47 |
| Block: 3584 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4302 | RingCT/type: yes/0 |
| Extra: 01f9895bd40bc15b845602c744189e2f5d1ba6ccc132a25a692ecbc35365b6bcee02090000000326697be300 | ||
1 output(s) for total of 34.944740557902 HMNY
| stealth address | amount | amount idx | tag |
| 00: 430b9761ffb2d6cde797a7976405d67ef9ede195590390f46e7922963d6ce6ef | 34.944740557902 | 4327 of 0 | <e2> |
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": 3644,
"vin": [ {
"gen": {
"height": 3584
}
}
],
"vout": [ {
"amount": 34944740557902,
"target": {
"tagged_key": {
"key": "430b9761ffb2d6cde797a7976405d67ef9ede195590390f46e7922963d6ce6ef",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 249, 137, 91, 212, 11, 193, 91, 132, 86, 2, 199, 68, 24, 158, 47, 93, 27, 166, 204, 193, 50, 162, 90, 105, 46, 203, 195, 83, 101, 182, 188, 238, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}