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: 1309f84c620e2b24eb594df156d5af16347f0e4fc4276881370b528a4c580d1d
Tx prefix hash: b1e0d611dd091847f12ce60d2604ebe438d23cf6c7672211db56d6b6ad7f8d0f
Tx public key: c7c9d66d9a127383337a23f1c7d2364b26cb735fefac57ed72d32f659f283d7f
| Timestamp: 1779923148 | Timestamp [UTC]: 2026-05-27 23:05:48 | Age [y:d:h:m:s]: 00:012:03:44:00 |
| Block: 3363 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4537 | RingCT/type: yes/0 |
| Extra: 01c7c9d66d9a127383337a23f1c7d2364b26cb735fefac57ed72d32f659f283d7f02090000000226697be300 | ||
1 output(s) for total of 34.959473725417 HMNY
| stealth address | amount | amount idx | tag |
| 00: 18aa7f8f4b29db84d00766047341c1073b5807cb21b07857f6d73c7531f1df4a | 34.959473725417 | 4052 of 0 | <93> |
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": 3423,
"vin": [ {
"gen": {
"height": 3363
}
}
],
"vout": [ {
"amount": 34959473725417,
"target": {
"tagged_key": {
"key": "18aa7f8f4b29db84d00766047341c1073b5807cb21b07857f6d73c7531f1df4a",
"view_tag": "93"
}
}
}
],
"extra": [ 1, 199, 201, 214, 109, 154, 18, 115, 131, 51, 122, 35, 241, 199, 210, 54, 75, 38, 203, 115, 95, 239, 172, 87, 237, 114, 211, 47, 101, 159, 40, 61, 127, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}