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: 9826df1d812af68260553199d288591b8a8725597bd3b363824f50fea5e4cda9
Tx prefix hash: d3d43b93d6340116551dcf21787187b54b22ee212e19a32d7982b7565873d024
Tx public key: 4de08294cae5f7c6a361ac9d64198f07dacc2608368c29eb3c6ba83c26cff772
| Timestamp: 1780818694 | Timestamp [UTC]: 2026-06-07 07:51:34 | Age [y:d:h:m:s]: 00:001:18:58:14 |
| Block: 7120 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 780 | RingCT/type: yes/0 |
| Extra: 014de08294cae5f7c6a361ac9d64198f07dacc2608368c29eb3c6ba83c26cff772020900000001e49593ff00 | ||
1 output(s) for total of 34.709852535993 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7433ae8b0e8b3165c1efe8d8d4b8be76cac76c80deff7d615e80c76a0449183f | 34.709852535993 | 8776 of 0 | <7d> |
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": 7180,
"vin": [ {
"gen": {
"height": 7120
}
}
],
"vout": [ {
"amount": 34709852535993,
"target": {
"tagged_key": {
"key": "7433ae8b0e8b3165c1efe8d8d4b8be76cac76c80deff7d615e80c76a0449183f",
"view_tag": "7d"
}
}
}
],
"extra": [ 1, 77, 224, 130, 148, 202, 229, 247, 198, 163, 97, 172, 157, 100, 25, 143, 7, 218, 204, 38, 8, 54, 140, 41, 235, 60, 107, 168, 60, 38, 207, 247, 114, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}