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: 803b826465160e1c8848ac0e0165249a9a1a307840d9502583fe7327ab559ad2
Tx prefix hash: 946b96c082efb18ec4e7973f4a04cc24606e8b71b6e7ee30af0aaf9ba848d525
Tx public key: 0c850ce23aed8cc2c986d2d9cf27ed54f1d44f4a999087a4f6895dad7ec56762
| Timestamp: 1779436341 | Timestamp [UTC]: 2026-05-22 07:52:21 | Age [y:d:h:m:s]: 00:017:20:40:41 |
| Block: 136 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 7896 | RingCT/type: yes/0 |
| Extra: 010c850ce23aed8cc2c986d2d9cf27ed54f1d44f4a999087a4f6895dad7ec56762 | ||
1 output(s) for total of 35.175313549967 HMNY
| stealth address | amount | amount idx | tag |
| 00: d95ad4db7952b96b67a4ff377996c7ca861e28669f41ebd0f6877ea49c682649 | 35.175313549967 | 132 of 0 | <35> |
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": 196,
"vin": [ {
"gen": {
"height": 136
}
}
],
"vout": [ {
"amount": 35175313549967,
"target": {
"tagged_key": {
"key": "d95ad4db7952b96b67a4ff377996c7ca861e28669f41ebd0f6877ea49c682649",
"view_tag": "35"
}
}
}
],
"extra": [ 1, 12, 133, 12, 226, 58, 237, 140, 194, 201, 134, 210, 217, 207, 39, 237, 84, 241, 212, 79, 74, 153, 144, 135, 164, 246, 137, 93, 173, 126, 197, 103, 98
],
"rct_signatures": {
"type": 0
}
}