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: 847da60982ea9646444f57c1a54d2fcbd2eadb08d6b3bb98487461d935034a9b
Tx prefix hash: a9b412b0fb260646eb2518209e5d06bc0e2bb975910b6ce09f34f86d2dc94f6d
Tx public key: e278c83788065130b4894b6671871ef8ec335650c44fb796d3892dedab6ee1fc
| Timestamp: 1779636325 | Timestamp [UTC]: 2026-05-24 15:25:25 | Age [y:d:h:m:s]: 00:023:17:03:47 |
| Block: 1106 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7639 | RingCT/type: yes/0 |
| Extra: 01e278c83788065130b4894b6671871ef8ec335650c44fb796d3892dedab6ee1fc020900000001ba6d17be00 | ||
1 output(s) for total of 35.110294814382 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1d36f3a31fe22b1582e2de79ef39f21df7f41178b98a5513c32c21ba09e37c40 | 35.110294814382 | 1246 of 0 | <64> |
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": 1166,
"vin": [ {
"gen": {
"height": 1106
}
}
],
"vout": [ {
"amount": 35110294814382,
"target": {
"tagged_key": {
"key": "1d36f3a31fe22b1582e2de79ef39f21df7f41178b98a5513c32c21ba09e37c40",
"view_tag": "64"
}
}
}
],
"extra": [ 1, 226, 120, 200, 55, 136, 6, 81, 48, 180, 137, 75, 102, 113, 135, 30, 248, 236, 51, 86, 80, 196, 79, 183, 150, 211, 137, 45, 237, 171, 110, 225, 252, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}