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: 642721708d16469c333061d795327c14b5e9aa1b7b9d5cc2f791eccb7d6cf6f6
Tx prefix hash: 6459b5f5cc970e3523226bbb0bc1f45e68b4a1f9b2d0c40f24eef69df9eb3f40
Tx public key: 2d1541eef4f1bc7398d87f601b952f6ea7b9e3d658000996933a1b32a59115fd
| Timestamp: 1779886746 | Timestamp [UTC]: 2026-05-27 12:59:06 | Age [y:d:h:m:s]: 00:012:13:50:42 |
| Block: 3016 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4904 | RingCT/type: yes/0 |
| Extra: 012d1541eef4f1bc7398d87f601b952f6ea7b9e3d658000996933a1b32a59115fd02090000000226697be300 | ||
1 output(s) for total of 34.989225332937 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3b6972d1d0819e06b6afef1403986d4ba80c4e0d6747273eb1fbfb2439b2bf89 | 34.989225332937 | 3582 of 0 | <69> |
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": 3076,
"vin": [ {
"gen": {
"height": 3016
}
}
],
"vout": [ {
"amount": 34989225332937,
"target": {
"tagged_key": {
"key": "3b6972d1d0819e06b6afef1403986d4ba80c4e0d6747273eb1fbfb2439b2bf89",
"view_tag": "69"
}
}
}
],
"extra": [ 1, 45, 21, 65, 238, 244, 241, 188, 115, 152, 216, 127, 96, 27, 149, 47, 110, 167, 185, 227, 214, 88, 0, 9, 150, 147, 58, 27, 50, 165, 145, 21, 253, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}