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: 4f1348f631c5959c7cd0f4fa3e3fe445ec78c2fcc0046d825eebe1b1f31b9fce
Tx prefix hash: e19cf48c9598d00b563a733f5196a35ca87b80d54f64d7190e5a8a28a21a1837
Tx public key: b75c9aea9a86f4fd41f941db1308ef183a07ff9961e4d848cd605541ad37c746
| Timestamp: 1779787800 | Timestamp [UTC]: 2026-05-26 09:30:00 | Age [y:d:h:m:s]: 00:013:16:05:57 |
| Block: 2190 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5696 | RingCT/type: yes/0 |
| Extra: 01b75c9aea9a86f4fd41f941db1308ef183a07ff9961e4d848cd605541ad37c74602090000000126697be300 | ||
1 output(s) for total of 35.037776889924 HMNY
| stealth address | amount | amount idx | tag |
| 00: 90df9e5b17063df24928a4e90354b421a83e4261e97428c675a8e08450df83dd | 35.037776889924 | 2532 of 0 | <86> |
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": 2250,
"vin": [ {
"gen": {
"height": 2190
}
}
],
"vout": [ {
"amount": 35037776889924,
"target": {
"tagged_key": {
"key": "90df9e5b17063df24928a4e90354b421a83e4261e97428c675a8e08450df83dd",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 183, 92, 154, 234, 154, 134, 244, 253, 65, 249, 65, 219, 19, 8, 239, 24, 58, 7, 255, 153, 97, 228, 216, 72, 205, 96, 85, 65, 173, 55, 199, 70, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}