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: c37f607f6d9fc428a4146f58c44c14ecfa9816051da1916fd3ec76cd8725d80d
Tx prefix hash: f6564e7155040d1ce70d2b034c7e15c2f5cc9a7fa0dbf063567fa582d2631fb0
Tx public key: c841ee3a227619206f53b5ccc7f1b3d0a42799c5150366ac834a6207085e86eb
| Timestamp: 1779640467 | Timestamp [UTC]: 2026-05-24 16:34:27 | Age [y:d:h:m:s]: 00:015:11:04:23 |
| Block: 1296 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6649 | RingCT/type: yes/0 |
| Extra: 01c841ee3a227619206f53b5ccc7f1b3d0a42799c5150366ac834a6207085e86eb020900000001ba6d17be00 | ||
1 output(s) for total of 35.097573268675 HMNY
| stealth address | amount | amount idx | tag |
| 00: dcd21f8f425a99149b739ff38ce73b58d2851d60b9e8484278ef29373996f167 | 35.097573268675 | 1444 of 0 | <c8> |
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": 1356,
"vin": [ {
"gen": {
"height": 1296
}
}
],
"vout": [ {
"amount": 35097573268675,
"target": {
"tagged_key": {
"key": "dcd21f8f425a99149b739ff38ce73b58d2851d60b9e8484278ef29373996f167",
"view_tag": "c8"
}
}
}
],
"extra": [ 1, 200, 65, 238, 58, 34, 118, 25, 32, 111, 83, 181, 204, 199, 241, 179, 208, 164, 39, 153, 197, 21, 3, 102, 172, 131, 74, 98, 7, 8, 94, 134, 235, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}