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: 1de3574d7f8834b84555d81c4f2b825dd467100ccd55243754b27ea11a152133
Tx prefix hash: f0e4084ff09cfedcd6c37fe4311aacbe5f1cc56f0cc48ce3816e87e195d59106
Tx public key: 61e7a51e565e9378f66d30c94614f2ca4b7e2f15c617b118327ec4aea1a2c2a9
| Timestamp: 1780860567 | Timestamp [UTC]: 2026-06-07 19:29:27 | Age [y:d:h:m:s]: 00:001:03:49:26 |
| Block: 7612 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 274 | RingCT/type: yes/0 |
| Extra: 0161e7a51e565e9378f66d30c94614f2ca4b7e2f15c617b118327ec4aea1a2c2a9020900000001e49593ff00 | ||
1 output(s) for total of 34.679923518767 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7643206f015a75a227e693348b60e59f224ecd542f437c79da02e6cc2830e0ad | 34.679923518767 | 9406 of 0 | <e7> |
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": 7672,
"vin": [ {
"gen": {
"height": 7612
}
}
],
"vout": [ {
"amount": 34679923518767,
"target": {
"tagged_key": {
"key": "7643206f015a75a227e693348b60e59f224ecd542f437c79da02e6cc2830e0ad",
"view_tag": "e7"
}
}
}
],
"extra": [ 1, 97, 231, 165, 30, 86, 94, 147, 120, 246, 109, 48, 201, 70, 20, 242, 202, 75, 126, 47, 21, 198, 23, 177, 24, 50, 126, 196, 174, 161, 162, 194, 169, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}