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: 021e661d2357b260a14869d667a082ca631182a857fbb04ed6ae24fd9a3b4ae4
Tx prefix hash: e8daa145b96f8799d063e00e62d7da538a90c535ac421fa77ef6faeda9a26155
Tx public key: e156f213388ca5f7c276baf8db4c0d584d26ea311269f0b9b1acf05fda6d72a4
| Timestamp: 1780979182 | Timestamp [UTC]: 2026-06-09 04:26:22 | Age [y:d:h:m:s]: 00:000:08:11:23 |
| Block: 7997 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 576 | RingCT/type: yes/0 |
| Extra: 01e156f213388ca5f7c276baf8db4c0d584d26ea311269f0b9b1acf05fda6d72a4020900000002e49593ff00 | ||
1 output(s) for total of 34.651840290398 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7470be20e3a71d5918dc62fa1b115ddfc50eccaaffdebc4391581e2bcb9d9f36 | 34.651840290398 | 9915 of 0 | <71> |
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": 8057,
"vin": [ {
"gen": {
"height": 7997
}
}
],
"vout": [ {
"amount": 34651840290398,
"target": {
"tagged_key": {
"key": "7470be20e3a71d5918dc62fa1b115ddfc50eccaaffdebc4391581e2bcb9d9f36",
"view_tag": "71"
}
}
}
],
"extra": [ 1, 225, 86, 242, 19, 56, 140, 165, 247, 194, 118, 186, 248, 219, 76, 13, 88, 77, 38, 234, 49, 18, 105, 240, 185, 177, 172, 240, 95, 218, 109, 114, 164, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}