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: bdb292c6f6a20ff1adf382f8f0bba47cdcb98c6862eb6fd3c0f5b22f082c6987
Tx prefix hash: f1688fe7d92eb78bdaac9df8fa3d18e60cff719c7bd4587904aa9c481e4754a3
Tx public key: c1bf5952d210d5f7ce8ce6337353b2991cb6adbff17de0ac88847407180682a1
| Timestamp: 1781012956 | Timestamp [UTC]: 2026-06-09 13:49:16 | Age [y:d:h:m:s]: 00:006:04:25:26 |
| Block: 8604 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 141 | RingCT/type: yes/0 |
| Extra: 01c1bf5952d210d5f7ce8ce6337353b2991cb6adbff17de0ac88847407180682a1020900000002e49593ff00 | ||
1 output(s) for total of 34.611744930950 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7274f03442cce6626a561afd75b310993ad809da9a3cb49fa7611e0e6e2d6a95 | 34.611744930950 | 10632 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": 8664,
"vin": [ {
"gen": {
"height": 8604
}
}
],
"vout": [ {
"amount": 34611744930950,
"target": {
"tagged_key": {
"key": "7274f03442cce6626a561afd75b310993ad809da9a3cb49fa7611e0e6e2d6a95",
"view_tag": "35"
}
}
}
],
"extra": [ 1, 193, 191, 89, 82, 210, 16, 213, 247, 206, 140, 230, 51, 115, 83, 178, 153, 28, 182, 173, 191, 241, 125, 224, 172, 136, 132, 116, 7, 24, 6, 130, 161, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}