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: aeae5e653eb1fe0878a2da29fb0169a64a38ea64500ca9de3a461c9bbad2fade
Tx prefix hash: e40ca85f62f6e12289057a5291c622c5fcfaecfb77425494828bce211af88cce
Tx public key: 2bcd3e9b270f617f290eb99471b65ad1c6bddace0b5082d817ac74c0b6ff4567
| Timestamp: 1780895873 | Timestamp [UTC]: 2026-06-08 05:17:53 | Age [y:d:h:m:s]: 00:001:11:51:10 |
| Block: 7764 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 969 | RingCT/type: yes/0 |
| Extra: 012bcd3e9b270f617f290eb99471b65ad1c6bddace0b5082d817ac74c0b6ff45670209000000014a728a4c00 | ||
1 output(s) for total of 34.667243429173 HMNY
| stealth address | amount | amount idx | tag |
| 00: eae8728d95afbc072a95199ef582ce453ad5ab81a21c48d0f87865ff2404848b | 34.667243429173 | 9616 of 0 | <fb> |
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": 7824,
"vin": [ {
"gen": {
"height": 7764
}
}
],
"vout": [ {
"amount": 34667243429173,
"target": {
"tagged_key": {
"key": "eae8728d95afbc072a95199ef582ce453ad5ab81a21c48d0f87865ff2404848b",
"view_tag": "fb"
}
}
}
],
"extra": [ 1, 43, 205, 62, 155, 39, 15, 97, 127, 41, 14, 185, 148, 113, 182, 90, 209, 198, 189, 218, 206, 11, 80, 130, 216, 23, 172, 116, 192, 182, 255, 69, 103, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}