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: 0a82bf1864d4ff75b1b0b15aceb9571925aa0c68e0ec3d2c26f942a25f93453e
Tx prefix hash: 4288acd9827fbc711fa070aac9fbcade01b15a74c9c2b5b5ab69abfee5ab35c5
Tx public key: d8c4170bf9cfd8ab60c9ed6ef1a1aef5b3e895204d1a3a72d64520344c6e3629
| Timestamp: 1780977871 | Timestamp [UTC]: 2026-06-09 04:04:31 | Age [y:d:h:m:s]: 00:000:11:55:13 |
| Block: 7964 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 727 | RingCT/type: yes/0 |
| Extra: 01d8c4170bf9cfd8ab60c9ed6ef1a1aef5b3e895204d1a3a72d64520344c6e3629020900000001e49593ff00 | ||
1 output(s) for total of 34.654021434748 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0f3e5ae283b2ece57d873d19544aea2f8975833f56cf1a228c333efa2c30f593 | 34.654021434748 | 9878 of 0 | <88> |
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": 8024,
"vin": [ {
"gen": {
"height": 7964
}
}
],
"vout": [ {
"amount": 34654021434748,
"target": {
"tagged_key": {
"key": "0f3e5ae283b2ece57d873d19544aea2f8975833f56cf1a228c333efa2c30f593",
"view_tag": "88"
}
}
}
],
"extra": [ 1, 216, 196, 23, 11, 249, 207, 216, 171, 96, 201, 237, 110, 241, 161, 174, 245, 179, 232, 149, 32, 77, 26, 58, 114, 214, 69, 32, 52, 76, 110, 54, 41, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}