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: 28398709d8bcc9197e713219e5c80c2ca559807f1c9e5d29700ab4f0eb0a10f7
Tx prefix hash: 19b41054cea8c30f4b641247343dc804a18119a53885b17fc0299ef42abc0707
Tx public key: a849f1c83784d6f7b705b28c95f802ec410e19be41be6357282fd76ec9f5d4e1
| Timestamp: 1779713777 | Timestamp [UTC]: 2026-05-25 12:56:17 | Age [y:d:h:m:s]: 00:014:11:50:30 |
| Block: 1603 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6283 | RingCT/type: yes/0 |
| Extra: 01a849f1c83784d6f7b705b28c95f802ec410e19be41be6357282fd76ec9f5d4e1020900000001ba6d17be00 | ||
1 output(s) for total of 35.077027669293 HMNY
| stealth address | amount | amount idx | tag |
| 00: bf54e7232309fedc8a1c61e74da7a7866dc4f1d0b2898ef1e9b6e274c02597c8 | 35.077027669293 | 1761 of 0 | <31> |
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": 1663,
"vin": [ {
"gen": {
"height": 1603
}
}
],
"vout": [ {
"amount": 35077027669293,
"target": {
"tagged_key": {
"key": "bf54e7232309fedc8a1c61e74da7a7866dc4f1d0b2898ef1e9b6e274c02597c8",
"view_tag": "31"
}
}
}
],
"extra": [ 1, 168, 73, 241, 200, 55, 132, 214, 247, 183, 5, 178, 140, 149, 248, 2, 236, 65, 14, 25, 190, 65, 190, 99, 87, 40, 47, 215, 110, 201, 245, 212, 225, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}