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: 13f84b171eae5ae381d0ac4d84d8f6ffa95b54e8c91fae6bce40152121d618d4
Tx prefix hash: 8393d49d8b8d7232d584d0cb43472c55bd8031a39678eee7e08b6e8009e6fdb1
Tx public key: e32787bea0482d19ce4b8ebf87ed7434ff4df79cf9cc8db62378aea47a98d8cd
| Timestamp: 1779639901 | Timestamp [UTC]: 2026-05-24 16:25:01 | Age [y:d:h:m:s]: 00:015:08:21:46 |
| Block: 1266 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6620 | RingCT/type: yes/0 |
| Extra: 01e32787bea0482d19ce4b8ebf87ed7434ff4df79cf9cc8db62378aea47a98d8cd020900000002ba6d17be00 | ||
1 output(s) for total of 35.099581627301 HMNY
| stealth address | amount | amount idx | tag |
| 00: 78c1b679c4f1e036ee108c28f0ef76da6bdbbb1b9d355112f7df39e57e9877aa | 35.099581627301 | 1412 of 0 | <9d> |
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": 1326,
"vin": [ {
"gen": {
"height": 1266
}
}
],
"vout": [ {
"amount": 35099581627301,
"target": {
"tagged_key": {
"key": "78c1b679c4f1e036ee108c28f0ef76da6bdbbb1b9d355112f7df39e57e9877aa",
"view_tag": "9d"
}
}
}
],
"extra": [ 1, 227, 39, 135, 190, 160, 72, 45, 25, 206, 75, 142, 191, 135, 237, 116, 52, 255, 77, 247, 156, 249, 204, 141, 182, 35, 120, 174, 164, 122, 152, 216, 205, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}