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: 0362f89bd1cf4a6cb96b127de645213389f8617ae553048f523d9cfbb53e3800
Tx prefix hash: 720bcfde2c8b3bba54dcd93ef5601597613527d45385b7a60f84e9d4176b9609
Tx public key: 93a807df7c1be861372ca1147e60d6cfed2eb4865f1b045bf3f9a4eb01d9f749
| Timestamp: 1780690374 | Timestamp [UTC]: 2026-06-05 20:12:54 | Age [y:d:h:m:s]: 00:003:06:36:54 |
| Block: 5656 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2244 | RingCT/type: yes/0 |
| Extra: 0193a807df7c1be861372ca1147e60d6cfed2eb4865f1b045bf3f9a4eb01d9f749020900000001e49593ff00 | ||
1 output(s) for total of 34.806910423931 HMNY
| stealth address | amount | amount idx | tag |
| 00: 231a51a8dfb194132ff866ce63fd14ba7b02ce8acdad1238b625ba4862185590 | 34.806910423931 | 7105 of 0 | <8c> |
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": 5716,
"vin": [ {
"gen": {
"height": 5656
}
}
],
"vout": [ {
"amount": 34806910423931,
"target": {
"tagged_key": {
"key": "231a51a8dfb194132ff866ce63fd14ba7b02ce8acdad1238b625ba4862185590",
"view_tag": "8c"
}
}
}
],
"extra": [ 1, 147, 168, 7, 223, 124, 27, 232, 97, 55, 44, 161, 20, 126, 96, 214, 207, 237, 46, 180, 134, 95, 27, 4, 91, 243, 249, 164, 235, 1, 217, 247, 73, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}