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: cd771ae465b2a40a08b402baad031be44c7970aa4b7150fca3da3d56446049c3
Tx prefix hash: 2f6d238a94d913e0854aa6747dfcc5c63bcc3bcec1b73f3b8d5d56de91f65d0b
Tx public key: 4a9206a7ea2ccec408e1ca05d9194363fc6b276a47bbf9bfb9d95e368e186b7e
| Timestamp: 1780976184 | Timestamp [UTC]: 2026-06-09 03:36:24 | Age [y:d:h:m:s]: 00:000:02:34:31 |
| Block: 7937 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 205 | RingCT/type: yes/0 |
| Extra: 014a9206a7ea2ccec408e1ca05d9194363fc6b276a47bbf9bfb9d95e368e186b7e020900000003e49593ff00 | ||
1 output(s) for total of 34.655806109514 HMNY
| stealth address | amount | amount idx | tag |
| 00: 16451d914fbdb5f4139370cfbceef83135b4f47d3a23168ebd93fffd10746a34 | 34.655806109514 | 9843 of 0 | <e9> |
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": 7997,
"vin": [ {
"gen": {
"height": 7937
}
}
],
"vout": [ {
"amount": 34655806109514,
"target": {
"tagged_key": {
"key": "16451d914fbdb5f4139370cfbceef83135b4f47d3a23168ebd93fffd10746a34",
"view_tag": "e9"
}
}
}
],
"extra": [ 1, 74, 146, 6, 167, 234, 44, 206, 196, 8, 225, 202, 5, 217, 25, 67, 99, 252, 107, 39, 106, 71, 187, 249, 191, 185, 217, 94, 54, 142, 24, 107, 126, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}