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: 66a33b244a6f8d6fef087f7496b0be13220cae653593229f510653e3821b6767
Tx prefix hash: 2155652bf0fad3c120cef58b689f98e9133d401aa305a6f28bcc9b4c9943c991
Tx public key: a38f72acc18146713a7c5d9cf4e5d50ba3f9e28532ef69769f96c6953b3ac9f2
| Timestamp: 1780763454 | Timestamp [UTC]: 2026-06-06 16:30:54 | Age [y:d:h:m:s]: 00:002:08:15:53 |
| Block: 6596 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1290 | RingCT/type: yes/0 |
| Extra: 01a38f72acc18146713a7c5d9cf4e5d50ba3f9e28532ef69769f96c6953b3ac9f2020900000001e49593ff00 | ||
1 output(s) for total of 34.744560696596 HMNY
| stealth address | amount | amount idx | tag |
| 00: a514ae6d740fa870af8b7ea0b664582601b60ecc3fb4b602511beff42192c0e1 | 34.744560696596 | 8126 of 0 | <e0> |
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": 6656,
"vin": [ {
"gen": {
"height": 6596
}
}
],
"vout": [ {
"amount": 34744560696596,
"target": {
"tagged_key": {
"key": "a514ae6d740fa870af8b7ea0b664582601b60ecc3fb4b602511beff42192c0e1",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 163, 143, 114, 172, 193, 129, 70, 113, 58, 124, 93, 156, 244, 229, 213, 11, 163, 249, 226, 133, 50, 239, 105, 118, 159, 150, 198, 149, 59, 58, 201, 242, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}