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: 83db7e918500b763951b566f0c2e11260fabb3bd1e5b5c59ed4ad7923f1c8bc3
Tx prefix hash: 962fd2b55b07283451282a1d22959baff48f52ff817fbbff357ad2f3b20d3173
Tx public key: 4c3699709e4d39b5d8844c663458d4376bd7f0d0607c041b6fc0a610e0fb7899
| Timestamp: 1780990100 | Timestamp [UTC]: 2026-06-09 07:28:20 | Age [y:d:h:m:s]: 00:000:08:31:24 |
| Block: 8211 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 480 | RingCT/type: yes/0 |
| Extra: 014c3699709e4d39b5d8844c663458d4376bd7f0d0607c041b6fc0a610e0fb7899020900000001e49593ff00 | ||
1 output(s) for total of 34.637699231102 HMNY
| stealth address | amount | amount idx | tag |
| 00: a111537a79b31296e79b6b212bb6e3817ee1e0667a95b62075be9e5d6a10f420 | 34.637699231102 | 10165 of 0 | <ad> |
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": 8271,
"vin": [ {
"gen": {
"height": 8211
}
}
],
"vout": [ {
"amount": 34637699231102,
"target": {
"tagged_key": {
"key": "a111537a79b31296e79b6b212bb6e3817ee1e0667a95b62075be9e5d6a10f420",
"view_tag": "ad"
}
}
}
],
"extra": [ 1, 76, 54, 153, 112, 158, 77, 57, 181, 216, 132, 76, 102, 52, 88, 212, 55, 107, 215, 240, 208, 96, 124, 4, 27, 111, 192, 166, 16, 224, 251, 120, 153, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}