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: 2aeff308736d43ed461ff5449576ecc328531eaeccd6fdddb1e9363e9624043e
Tx prefix hash: 7e9e0e07af46fd171f7042e5ab9d4c69140c71e864462e62b5169c9160dfe2fc
Tx public key: 820375bf1cc509fdf08d638639461a0e22b4c67199f22acb3f868115f74e27ef
| Timestamp: 1779451951 | Timestamp [UTC]: 2026-05-22 12:12:31 | Age [y:d:h:m:s]: 00:018:04:56:32 |
| Block: 340 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8394 | RingCT/type: yes/0 |
| Extra: 01820375bf1cc509fdf08d638639461a0e22b4c67199f22acb3f868115f74e27ef0209000000024438f87f00 | ||
1 output(s) for total of 35.161629515726 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6f06fd5d68727378e8110faf97fa8e1fcf8bc35f1e289a3c1070dbd2e405affd | 35.161629515726 | 336 of 0 | <03> |
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": 400,
"vin": [ {
"gen": {
"height": 340
}
}
],
"vout": [ {
"amount": 35161629515726,
"target": {
"tagged_key": {
"key": "6f06fd5d68727378e8110faf97fa8e1fcf8bc35f1e289a3c1070dbd2e405affd",
"view_tag": "03"
}
}
}
],
"extra": [ 1, 130, 3, 117, 191, 28, 197, 9, 253, 240, 141, 99, 134, 57, 70, 26, 14, 34, 180, 198, 113, 153, 242, 42, 203, 63, 134, 129, 21, 247, 78, 39, 239, 2, 9, 0, 0, 0, 2, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}