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: d596a57af8cc52eab40948ddbb28fbc76f1132a5de5aa231ae9ecaac3e1b5a78
Tx prefix hash: f144da7cc592480cb9d91cf2d821b764135b697b7b56ef5dd4e6656293cf8575
Tx public key: a9c20ecf642e774397a46b92e1b9cdf9880375beb08358be128f477add410c5f
| Timestamp: 1781004579 | Timestamp [UTC]: 2026-06-09 11:29:39 | Age [y:d:h:m:s]: 00:003:23:32:37 |
| Block: 8512 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 233 | RingCT/type: yes/0 |
| Extra: 01a9c20ecf642e774397a46b92e1b9cdf9880375beb08358be128f477add410c5f020900000001e49593ff00 | ||
1 output(s) for total of 34.617819002777 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5b4c8ceedabdd4b4e7b63a8324da74d77f24207fbe73af3499e0c6b830ae502e | 34.617819002777 | 10516 of 0 | <23> |
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": 8572,
"vin": [ {
"gen": {
"height": 8512
}
}
],
"vout": [ {
"amount": 34617819002777,
"target": {
"tagged_key": {
"key": "5b4c8ceedabdd4b4e7b63a8324da74d77f24207fbe73af3499e0c6b830ae502e",
"view_tag": "23"
}
}
}
],
"extra": [ 1, 169, 194, 14, 207, 100, 46, 119, 67, 151, 164, 107, 146, 225, 185, 205, 249, 136, 3, 117, 190, 176, 131, 88, 190, 18, 143, 71, 122, 221, 65, 12, 95, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}