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: 5aed42f6dbb4cae99a0dc3058cffef21aabb6ccff3fa700c8731b39e98a29a24
Tx prefix hash: 6d2ca6b2a2a0fb05266031fb0fc88125645d60191c2a2cb9876cbc5398537c5a
Tx public key: 7bf1c15f72d9ebc4729b9be2836dfd7db29cd0a1a8419628db32b584b251f24f
| Timestamp: 1780706449 | Timestamp [UTC]: 2026-06-06 00:40:49 | Age [y:d:h:m:s]: 00:003:16:28:14 |
| Block: 6116 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2619 | RingCT/type: yes/0 |
| Extra: 017bf1c15f72d9ebc4729b9be2836dfd7db29cd0a1a8419628db32b584b251f24f020900000003e49593ff00 | ||
1 output(s) for total of 34.776384888046 HMNY
| stealth address | amount | amount idx | tag |
| 00: 59b9950b3a89940d79f4f60f72013e77dd3b4b2aee2a555803169ca951df1b1b | 34.776384888046 | 7589 of 0 | <34> |
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": 6176,
"vin": [ {
"gen": {
"height": 6116
}
}
],
"vout": [ {
"amount": 34776384888046,
"target": {
"tagged_key": {
"key": "59b9950b3a89940d79f4f60f72013e77dd3b4b2aee2a555803169ca951df1b1b",
"view_tag": "34"
}
}
}
],
"extra": [ 1, 123, 241, 193, 95, 114, 217, 235, 196, 114, 155, 155, 226, 131, 109, 253, 125, 178, 156, 208, 161, 168, 65, 150, 40, 219, 50, 181, 132, 178, 81, 242, 79, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}