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: 00537bc29f7cb1eb2b7b523f08d31262cf7333ddba1cbea6faa8dee4e04f688f
Tx prefix hash: 6a74811841e06852a447947d60075a194506b7a22ce9a287553501a906fe4365
Tx public key: 6644156edc8377a6e7d016e4b3f05ef88d4bfd52bbdaf4d0084a161db9619986
| Timestamp: 1779473814 | Timestamp [UTC]: 2026-05-22 18:16:54 | Age [y:d:h:m:s]: 00:017:10:16:08 |
| Block: 595 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7420 | RingCT/type: yes/0 |
| Extra: 016644156edc8377a6e7d016e4b3f05ef88d4bfd52bbdaf4d0084a161db961998602090000000293369e7d00 | ||
1 output(s) for total of 35.144531958734 HMNY
| stealth address | amount | amount idx | tag |
| 00: fb268d0fe4fb78c429c30d2749cfff6b647145b40b91f709c9d01caf91491d9b | 35.144531958734 | 609 of 0 | <cc> |
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": 655,
"vin": [ {
"gen": {
"height": 595
}
}
],
"vout": [ {
"amount": 35144531958734,
"target": {
"tagged_key": {
"key": "fb268d0fe4fb78c429c30d2749cfff6b647145b40b91f709c9d01caf91491d9b",
"view_tag": "cc"
}
}
}
],
"extra": [ 1, 102, 68, 21, 110, 220, 131, 119, 166, 231, 208, 22, 228, 179, 240, 94, 248, 141, 75, 253, 82, 187, 218, 244, 208, 8, 74, 22, 29, 185, 97, 153, 134, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}