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: 6600305171d89340573304008f6a5e93ac9ab827f4612c067df901f230618c70
Tx prefix hash: 891b10b0f5241db7d03025dca92c160f2380799a942466108d2010eb6b8e7bfb
Tx public key: 472ddd9e4e1c31855f838478e5e50433848818e6b86196b9ac2088ceea6d45b2
| Timestamp: 1779473678 | Timestamp [UTC]: 2026-05-22 18:14:38 | Age [y:d:h:m:s]: 00:017:08:35:10 |
| Block: 592 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7308 | RingCT/type: yes/0 |
| Extra: 01472ddd9e4e1c31855f838478e5e50433848818e6b86196b9ac2088ceea6d45b202090000000293369e7d00 | ||
1 output(s) for total of 35.156827858127 HMNY
| stealth address | amount | amount idx | tag |
| 00: e4871eeb0a3349befe7f811efa9aae86cf38dd542d10aab6da37e94cae341e98 | 35.156827858127 | 604 of 0 | <a3> |
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": 652,
"vin": [ {
"gen": {
"height": 592
}
}
],
"vout": [ {
"amount": 35156827858127,
"target": {
"tagged_key": {
"key": "e4871eeb0a3349befe7f811efa9aae86cf38dd542d10aab6da37e94cae341e98",
"view_tag": "a3"
}
}
}
],
"extra": [ 1, 71, 45, 221, 158, 78, 28, 49, 133, 95, 131, 132, 120, 229, 229, 4, 51, 132, 136, 24, 230, 184, 97, 150, 185, 172, 32, 136, 206, 234, 109, 69, 178, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}