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: 3c7d5576554b6c6c6f95b582aa46e5d093a2d2133411572826b7025148bb78ff
Tx prefix hash: c5cc27e145215cd1a623a3d4ba12ffa6702f27853940586568a510da7df49e15
Tx public key: 9c3995b38d531ead1a262391f36b084ee418983c5c302dc6a19ab7cc2cd6db9e
| Timestamp: 1779629430 | Timestamp [UTC]: 2026-05-24 13:30:30 | Age [y:d:h:m:s]: 00:015:13:19:18 |
| Block: 832 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7088 | RingCT/type: yes/0 |
| Extra: 019c3995b38d531ead1a262391f36b084ee418983c5c302dc6a19ab7cc2cd6db9e020900000001ba6d17be00 | ||
1 output(s) for total of 35.128648742424 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5aa1fdaac996757bde90b0a720ec9099c2a75065a9677c418b09d70eb6ef42e8 | 35.128648742424 | 964 of 0 | <2e> |
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": 892,
"vin": [ {
"gen": {
"height": 832
}
}
],
"vout": [ {
"amount": 35128648742424,
"target": {
"tagged_key": {
"key": "5aa1fdaac996757bde90b0a720ec9099c2a75065a9677c418b09d70eb6ef42e8",
"view_tag": "2e"
}
}
}
],
"extra": [ 1, 156, 57, 149, 179, 141, 83, 30, 173, 26, 38, 35, 145, 243, 107, 8, 78, 228, 24, 152, 60, 92, 48, 45, 198, 161, 154, 183, 204, 44, 214, 219, 158, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}