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: 74d9fb40056b5b6dc2127e8a3bfdf552fe7b16c37bd82fac8d6ab5b6f7a2bcff
Tx prefix hash: df982d22c08c6b3888b7ed5bf7ad278544840471a43837c56f6dd3c1c6fa3339
Tx public key: 34c8f6ab312d79058db3faa1ea0eacc99e78871c16e0da559cf4c47b41d4397d
| Timestamp: 1780991267 | Timestamp [UTC]: 2026-06-09 07:47:47 | Age [y:d:h:m:s]: 00:000:04:45:40 |
| Block: 8235 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 335 | RingCT/type: yes/0 |
| Extra: 0134c8f6ab312d79058db3faa1ea0eacc99e78871c16e0da559cf4c47b41d4397d020900000001e49593ff00 | ||
1 output(s) for total of 34.636113677842 HMNY
| stealth address | amount | amount idx | tag |
| 00: dd48eae4556f149812b1f0fb40458ea938ef5fa48e6b0cbeaa755c3a384890d6 | 34.636113677842 | 10193 of 0 | <13> |
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": 8295,
"vin": [ {
"gen": {
"height": 8235
}
}
],
"vout": [ {
"amount": 34636113677842,
"target": {
"tagged_key": {
"key": "dd48eae4556f149812b1f0fb40458ea938ef5fa48e6b0cbeaa755c3a384890d6",
"view_tag": "13"
}
}
}
],
"extra": [ 1, 52, 200, 246, 171, 49, 45, 121, 5, 141, 179, 250, 161, 234, 14, 172, 201, 158, 120, 135, 28, 22, 224, 218, 85, 156, 244, 196, 123, 65, 212, 57, 125, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}