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: 0baa4e9f7fa17b19dfc561ef1849bd014546f25e7c666696fbe88ef1ecff05e8
Tx prefix hash: 716789416d05dc0d459c7fa345d573b6530eaf5a6a96aa1383488066a3c557a4
Tx public key: 149854292d04f3e0941f4442d064f1a24718f0940313ed20c7137c95046ec650
| Timestamp: 1779645110 | Timestamp [UTC]: 2026-05-24 17:51:50 | Age [y:d:h:m:s]: 00:023:14:44:24 |
| Block: 1441 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7304 | RingCT/type: yes/0 |
| Extra: 01149854292d04f3e0941f4442d064f1a24718f0940313ed20c7137c95046ec650020900000001ba6d17be00 | ||
1 output(s) for total of 35.087867821861 HMNY
| stealth address | amount | amount idx | tag |
| 00: 12e9320b8c96c6525dd43e88108576a5aaec6ace86a5aaf51da6a3ffba3edb1a | 35.087867821861 | 1595 of 0 | <ae> |
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": 1501,
"vin": [ {
"gen": {
"height": 1441
}
}
],
"vout": [ {
"amount": 35087867821861,
"target": {
"tagged_key": {
"key": "12e9320b8c96c6525dd43e88108576a5aaec6ace86a5aaf51da6a3ffba3edb1a",
"view_tag": "ae"
}
}
}
],
"extra": [ 1, 20, 152, 84, 41, 45, 4, 243, 224, 148, 31, 68, 66, 208, 100, 241, 162, 71, 24, 240, 148, 3, 19, 237, 32, 199, 19, 124, 149, 4, 110, 198, 80, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}