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: a69c318f2246294514d1810e239ebfc64faa3b3a57d14a636a23f3670c92dc43
Tx prefix hash: cb94837792514f14dcb087757de1391890a9d3982bed5fdc862856658c4740a9
Tx public key: b829a74d2b50c292e77dc135ccc3e2aeff0968c786c4709c5eea1e6dea3e62d8
| Timestamp: 1779954198 | Timestamp [UTC]: 2026-05-28 07:43:18 | Age [y:d:h:m:s]: 00:011:15:35:35 |
| Block: 3666 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4220 | RingCT/type: yes/0 |
| Extra: 01b829a74d2b50c292e77dc135ccc3e2aeff0968c786c4709c5eea1e6dea3e62d802090000000826697be300 | ||
1 output(s) for total of 34.939275532217 HMNY
| stealth address | amount | amount idx | tag |
| 00: 539391e63055788d2c1e13d3c91cef413111ce45eecb39a04fc71e04342f8826 | 34.939275532217 | 4430 of 0 | <c2> |
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": 3726,
"vin": [ {
"gen": {
"height": 3666
}
}
],
"vout": [ {
"amount": 34939275532217,
"target": {
"tagged_key": {
"key": "539391e63055788d2c1e13d3c91cef413111ce45eecb39a04fc71e04342f8826",
"view_tag": "c2"
}
}
}
],
"extra": [ 1, 184, 41, 167, 77, 43, 80, 194, 146, 231, 125, 193, 53, 204, 195, 226, 174, 255, 9, 104, 199, 134, 196, 112, 156, 94, 234, 30, 109, 234, 62, 98, 216, 2, 9, 0, 0, 0, 8, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}