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: 14aafd43de5a53553ee8b595762c017eab91b233134838455c0c3656161320ab
Tx prefix hash: 98179cdfe3071a937c763f4729b738c7785ce8149c5a62679051e70fd99fbce5
Tx public key: 439294af06521abb2d7999b97e17a1a0f73c6334953df3e0733106f59f935926
| Timestamp: 1779717089 | Timestamp [UTC]: 2026-05-25 13:51:29 | Age [y:d:h:m:s]: 00:014:12:58:19 |
| Block: 1671 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6238 | RingCT/type: yes/0 |
| Extra: 01439294af06521abb2d7999b97e17a1a0f73c6334953df3e0733106f59f935926020900000003ba6d17be00 | ||
1 output(s) for total of 35.072478479763 HMNY
| stealth address | amount | amount idx | tag |
| 00: d36ef1b426034f38e1bee718a971b4593435039855fea46b8e50787987c08c09 | 35.072478479763 | 1838 of 0 | <c8> |
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": 1731,
"vin": [ {
"gen": {
"height": 1671
}
}
],
"vout": [ {
"amount": 35072478479763,
"target": {
"tagged_key": {
"key": "d36ef1b426034f38e1bee718a971b4593435039855fea46b8e50787987c08c09",
"view_tag": "c8"
}
}
}
],
"extra": [ 1, 67, 146, 148, 175, 6, 82, 26, 187, 45, 121, 153, 185, 126, 23, 161, 160, 247, 60, 99, 52, 149, 61, 243, 224, 115, 49, 6, 245, 159, 147, 89, 38, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}