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: 8cca41dbf6c15afd86d443b1bbcbe611a81439fa0316b996add654ea4fc7f214
Tx prefix hash: 5737315fabf5aaabd6704805206e380e00e61e2d263a51d01d1a293fbcd77aad
Tx public key: 893d66a9dbf8ce069b3428a0f6f91e518407e165f6851be5ad6537967b195b2e
| Timestamp: 1779636276 | Timestamp [UTC]: 2026-05-24 15:24:36 | Age [y:d:h:m:s]: 00:015:10:11:21 |
| Block: 1101 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6785 | RingCT/type: yes/0 |
| Extra: 01893d66a9dbf8ce069b3428a0f6f91e518407e165f6851be5ad6537967b195b2e020900000001ba6d17be00 | ||
1 output(s) for total of 35.110629654162 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5707d4acd2de591b7d358761a0a4bfe591c15f8f5a9f776e0e1afe129756c48c | 35.110629654162 | 1241 of 0 | <40> |
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": 1161,
"vin": [ {
"gen": {
"height": 1101
}
}
],
"vout": [ {
"amount": 35110629654162,
"target": {
"tagged_key": {
"key": "5707d4acd2de591b7d358761a0a4bfe591c15f8f5a9f776e0e1afe129756c48c",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 137, 61, 102, 169, 219, 248, 206, 6, 155, 52, 40, 160, 246, 249, 30, 81, 132, 7, 225, 101, 246, 133, 27, 229, 173, 101, 55, 150, 123, 25, 91, 46, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}