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: 3526acad120b4922c65391e24d8a6a0a05cc0545e2825b9a38e332716b5d009c
Tx prefix hash: 31a04ae7ffd29df997229231b70463f11bc1310fd68a4cbdedbea5ab23b6148b
Tx public key: aae516e35efe34839e244d23f682c88c5f1eb64a5c7381e5c3652f426d533696
| Timestamp: 1780996448 | Timestamp [UTC]: 2026-06-09 09:14:08 | Age [y:d:h:m:s]: 00:000:14:07:26 |
| Block: 8347 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 398 | RingCT/type: yes/0 |
| Extra: 01aae516e35efe34839e244d23f682c88c5f1eb64a5c7381e5c3652f426d533696020900000001e49593ff00 | ||
1 output(s) for total of 34.628715388901 HMNY
| stealth address | amount | amount idx | tag |
| 00: 20f9d68dff2efa9547b0a57f38c5c92203718a6b1ff01bfdbf32028cd7c9e4c4 | 34.628715388901 | 10323 of 0 | <f6> |
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": 8407,
"vin": [ {
"gen": {
"height": 8347
}
}
],
"vout": [ {
"amount": 34628715388901,
"target": {
"tagged_key": {
"key": "20f9d68dff2efa9547b0a57f38c5c92203718a6b1ff01bfdbf32028cd7c9e4c4",
"view_tag": "f6"
}
}
}
],
"extra": [ 1, 170, 229, 22, 227, 94, 254, 52, 131, 158, 36, 77, 35, 246, 130, 200, 140, 95, 30, 182, 74, 92, 115, 129, 229, 195, 101, 47, 66, 109, 83, 54, 150, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}