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: 7c8d7df294cd3f7269721b6af87b963816cfbb781b63a69f5ef8f005b124ccdc
Tx prefix hash: eb754fd68b4ec13e79951341fece241076d093d98ace05076e5ba91ab7cab4ea
Tx public key: 35d3580d47cc3f939f4ef3f48f15205a0a897b34e34b09cb5aa8a9c4622a0350
| Timestamp: 1779738051 | Timestamp [UTC]: 2026-05-25 19:40:51 | Age [y:d:h:m:s]: 00:014:05:55:06 |
| Block: 1925 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5961 | RingCT/type: yes/0 |
| Extra: 0135d3580d47cc3f939f4ef3f48f15205a0a897b34e34b09cb5aa8a9c4622a035002090000000126697be300 | ||
1 output(s) for total of 35.055491136050 HMNY
| stealth address | amount | amount idx | tag |
| 00: b13e69a18b993e0f6a1519e43c74cff230bff5ce891f95700245d466efce376d | 35.055491136050 | 2167 of 0 | <41> |
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": 1985,
"vin": [ {
"gen": {
"height": 1925
}
}
],
"vout": [ {
"amount": 35055491136050,
"target": {
"tagged_key": {
"key": "b13e69a18b993e0f6a1519e43c74cff230bff5ce891f95700245d466efce376d",
"view_tag": "41"
}
}
}
],
"extra": [ 1, 53, 211, 88, 13, 71, 204, 63, 147, 159, 78, 243, 244, 143, 21, 32, 90, 10, 137, 123, 52, 227, 75, 9, 203, 90, 168, 169, 196, 98, 42, 3, 80, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}