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: 82059ed7dbca0402f31c25f6701ddfa3f3103ce0ee9caac5ae19d24a5081ca93
Tx prefix hash: 0560f3651c98913a820fee29ad93e2dede207c4725afc5d99e9aea6e09305273
Tx public key: 0b3e2076b3f4978a5e5bbc9154034e238050053f960534b0c8a15587c66c98a3
| Timestamp: 1780991144 | Timestamp [UTC]: 2026-06-09 07:45:44 | Age [y:d:h:m:s]: 00:000:04:47:43 |
| Block: 8232 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 339 | RingCT/type: yes/0 |
| Extra: 010b3e2076b3f4978a5e5bbc9154034e238050053f960534b0c8a15587c66c98a3020900000001e49593ff00 | ||
1 output(s) for total of 34.636311868030 HMNY
| stealth address | amount | amount idx | tag |
| 00: 959ee76141a00955291be6312b5d234fa75477829c0da30763cd00044cdb0c97 | 34.636311868030 | 10190 of 0 | <79> |
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": 8292,
"vin": [ {
"gen": {
"height": 8232
}
}
],
"vout": [ {
"amount": 34636311868030,
"target": {
"tagged_key": {
"key": "959ee76141a00955291be6312b5d234fa75477829c0da30763cd00044cdb0c97",
"view_tag": "79"
}
}
}
],
"extra": [ 1, 11, 62, 32, 118, 179, 244, 151, 138, 94, 91, 188, 145, 84, 3, 78, 35, 128, 80, 5, 63, 150, 5, 52, 176, 200, 161, 85, 135, 198, 108, 152, 163, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}