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: 5c0c594d882d7a0babcd7d0c208f1cb63ea56229bf1ff668707ffd424913afd9
Tx prefix hash: eab2de3fddeec377a1836c32c19ed2b329a6888e7da4171af8be2da13cee9106
Tx public key: 2f94fb27b751012f0a5431e3968640b6c0ed783b71e298e9ee7e3d66560a27b1
| Timestamp: 1779717697 | Timestamp [UTC]: 2026-05-25 14:01:37 | Age [y:d:h:m:s]: 00:014:07:10:30 |
| Block: 1691 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6195 | RingCT/type: yes/0 |
| Extra: 012f94fb27b751012f0a5431e3968640b6c0ed783b71e298e9ee7e3d66560a27b1020900000001ba6d17be00 | ||
1 output(s) for total of 35.071140595128 HMNY
| stealth address | amount | amount idx | tag |
| 00: e4d268e6245ef4097aa2634da2bfc267012c4c72ae06a289f1ac0bde92525fad | 35.071140595128 | 1860 of 0 | <da> |
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": 1751,
"vin": [ {
"gen": {
"height": 1691
}
}
],
"vout": [ {
"amount": 35071140595128,
"target": {
"tagged_key": {
"key": "e4d268e6245ef4097aa2634da2bfc267012c4c72ae06a289f1ac0bde92525fad",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 47, 148, 251, 39, 183, 81, 1, 47, 10, 84, 49, 227, 150, 134, 64, 182, 192, 237, 120, 59, 113, 226, 152, 233, 238, 126, 61, 102, 86, 10, 39, 177, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}