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: 6e7ceb9410fbbed9a219076e809cefceaecc272c9b113e64a11d774a10fb779d
Tx prefix hash: 57663b87f37fc032f7f706b7a4b6b548bbbfc952a413363fb44513823d6a024e
Tx public key: b3669961d971f942f96a16f157dae4eb7f15222710c41e28f77d9e5aa9c34e7a
| Timestamp: 1780010783 | Timestamp [UTC]: 2026-05-28 23:26:23 | Age [y:d:h:m:s]: 00:010:23:52:30 |
| Block: 4093 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3793 | RingCT/type: yes/0 |
| Extra: 01b3669961d971f942f96a16f157dae4eb7f15222710c41e28f77d9e5aa9c34e7a02090000000126697be300 | ||
1 output(s) for total of 34.913440020713 HMNY
| stealth address | amount | amount idx | tag |
| 00: 25680e3f34499895a33a81e57d1628f17f9e255dab717ae139d983afe7161822 | 34.913440020713 | 5092 of 0 | <a2> |
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": 4153,
"vin": [ {
"gen": {
"height": 4093
}
}
],
"vout": [ {
"amount": 34913440020713,
"target": {
"tagged_key": {
"key": "25680e3f34499895a33a81e57d1628f17f9e255dab717ae139d983afe7161822",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 179, 102, 153, 97, 217, 113, 249, 66, 249, 106, 22, 241, 87, 218, 228, 235, 127, 21, 34, 39, 16, 196, 30, 40, 247, 125, 158, 90, 169, 195, 78, 122, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}