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: d611914f7468636a2a0c93af7d99ba581bb2395f3fd45988e5b6ea55e4ae21f6
Tx prefix hash: 731d179b568e26952bcce943ae32077960c9e912184070fc3ca99c1595d815e4
Tx public key: 52f46c854be7e2c08a5df66dbc4a8f046b1ff7a1b17c51cfa96c6505956cd6a8
| Timestamp: 1780013961 | Timestamp [UTC]: 2026-05-29 00:19:21 | Age [y:d:h:m:s]: 00:011:00:27:26 |
| Block: 4110 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3776 | RingCT/type: yes/0 |
| Extra: 0152f46c854be7e2c08a5df66dbc4a8f046b1ff7a1b17c51cfa96c6505956cd6a802090000000526697be300 | ||
1 output(s) for total of 34.912315256840 HMNY
| stealth address | amount | amount idx | tag |
| 00: c7c0b26b0214151a3fe93c388d33621c0b80a9a70be19a94fe0139baf8304067 | 34.912315256840 | 5121 of 0 | <76> |
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": 4170,
"vin": [ {
"gen": {
"height": 4110
}
}
],
"vout": [ {
"amount": 34912315256840,
"target": {
"tagged_key": {
"key": "c7c0b26b0214151a3fe93c388d33621c0b80a9a70be19a94fe0139baf8304067",
"view_tag": "76"
}
}
}
],
"extra": [ 1, 82, 244, 108, 133, 75, 231, 226, 192, 138, 93, 246, 109, 188, 74, 143, 4, 107, 31, 247, 161, 177, 124, 81, 207, 169, 108, 101, 5, 149, 108, 214, 168, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}