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: 9e36905251b3b6584839efb6a4a365382daf3b0f29e508531f3b205df9b0b1be
Tx prefix hash: c3f5b9e9ab796b7d972b122b4b919fa05bcd83c80378c71e3bfbc772a6388227
Tx public key: 65068801128c6edaceb31eabc3aa7a046e4e3c417ce47e3c0cd846a9eaf2d107
| Timestamp: 1779470767 | Timestamp [UTC]: 2026-05-22 17:26:07 | Age [y:d:h:m:s]: 00:017:09:23:41 |
| Block: 559 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7341 | RingCT/type: yes/0 |
| Extra: 0165068801128c6edaceb31eabc3aa7a046e4e3c417ce47e3c0cd846a9eaf2d10702090000000393369e7d00 | ||
1 output(s) for total of 35.146945227387 HMNY
| stealth address | amount | amount idx | tag |
| 00: e61587f90dcf8811e76f770bdb02b945764b6070ac3ccc39e574dc9958eb774b | 35.146945227387 | 567 of 0 | <14> |
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": 619,
"vin": [ {
"gen": {
"height": 559
}
}
],
"vout": [ {
"amount": 35146945227387,
"target": {
"tagged_key": {
"key": "e61587f90dcf8811e76f770bdb02b945764b6070ac3ccc39e574dc9958eb774b",
"view_tag": "14"
}
}
}
],
"extra": [ 1, 101, 6, 136, 1, 18, 140, 110, 218, 206, 179, 30, 171, 195, 170, 122, 4, 110, 78, 60, 65, 124, 228, 126, 60, 12, 216, 70, 169, 234, 242, 209, 7, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}