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: a320d47381f300caeffd93b28237f61c336700f55387fe920193c0ac208a0d37
Tx prefix hash: f846eef183b13c7acab19d90baca1d6611cf138d59559e805d35b0f6c3665dfb
Tx public key: aa13c808d99b086c8c67f47c993133a85f22f5443fdc7e0aefa619d8ecf03da9
| Timestamp: 1779796258 | Timestamp [UTC]: 2026-05-26 11:50:58 | Age [y:d:h:m:s]: 00:013:14:58:50 |
| Block: 2270 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5629 | RingCT/type: yes/0 |
| Extra: 01aa13c808d99b086c8c67f47c993133a85f22f5443fdc7e0aefa619d8ecf03da902090000000426697be300 | ||
1 output(s) for total of 35.032430952231 HMNY
| stealth address | amount | amount idx | tag |
| 00: e793cdca5ea65e9fa27cfd521bbf1cff191777e32748c163ded275f0d2a46756 | 35.032430952231 | 2640 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": 2330,
"vin": [ {
"gen": {
"height": 2270
}
}
],
"vout": [ {
"amount": 35032430952231,
"target": {
"tagged_key": {
"key": "e793cdca5ea65e9fa27cfd521bbf1cff191777e32748c163ded275f0d2a46756",
"view_tag": "14"
}
}
}
],
"extra": [ 1, 170, 19, 200, 8, 217, 155, 8, 108, 140, 103, 244, 124, 153, 49, 51, 168, 95, 34, 245, 68, 63, 220, 126, 10, 239, 166, 25, 216, 236, 240, 61, 169, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}