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: 11421442ff46e41b158ec2294687bc8896d956ef7559c5a38764edef89d23226
Tx prefix hash: 0fef1c89e3be1009d338813c755c6eb4edde1ce1c09a68a055c7068600fae03b
Tx public key: c3f8af578abf309838ad0b3775f26dfc35c604c5caa04e7e3bc1d0f485c72110
| Timestamp: 1780782245 | Timestamp [UTC]: 2026-06-06 21:44:05 | Age [y:d:h:m:s]: 00:002:01:34:48 |
| Block: 6773 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1113 | RingCT/type: yes/0 |
| Extra: 01c3f8af578abf309838ad0b3775f26dfc35c604c5caa04e7e3bc1d0f485c72110020900000002e49593ff00 | ||
1 output(s) for total of 34.732832876893 HMNY
| stealth address | amount | amount idx | tag |
| 00: 201bf924037d13e919c4707b7f8c2b04a553d578e2dc9cea75096b1c99c80635 | 34.732832876893 | 8363 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": 6833,
"vin": [ {
"gen": {
"height": 6773
}
}
],
"vout": [ {
"amount": 34732832876893,
"target": {
"tagged_key": {
"key": "201bf924037d13e919c4707b7f8c2b04a553d578e2dc9cea75096b1c99c80635",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 195, 248, 175, 87, 138, 191, 48, 152, 56, 173, 11, 55, 117, 242, 109, 252, 53, 198, 4, 197, 202, 160, 78, 126, 59, 193, 208, 244, 133, 199, 33, 16, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}