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: df991b68f6c4f8db6f11b6956ac9a54282bc91ca2ebc196e70948b0c22f899da
Tx prefix hash: 7b3a872adc91ce0dda3ba58abfddb333c408f4cff4bf9d1d9525ad3fbb242652
Tx public key: dab68ab9b8ac0914946703b7e105717b7302960f6ef7ea00a5849fbe1c63b4d5
| Timestamp: 1779787482 | Timestamp [UTC]: 2026-05-26 09:24:42 | Age [y:d:h:m:s]: 00:020:03:15:27 |
| Block: 2185 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6560 | RingCT/type: yes/0 |
| Extra: 01dab68ab9b8ac0914946703b7e105717b7302960f6ef7ea00a5849fbe1c63b4d502090000000226697be300 | ||
1 output(s) for total of 35.038111038115 HMNY
| stealth address | amount | amount idx | tag |
| 00: e24340ad8278041b5507c034f801556462685d6eed08170fd6846b683a9d3af9 | 35.038111038115 | 2525 of 0 | <85> |
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": 2245,
"vin": [ {
"gen": {
"height": 2185
}
}
],
"vout": [ {
"amount": 35038111038115,
"target": {
"tagged_key": {
"key": "e24340ad8278041b5507c034f801556462685d6eed08170fd6846b683a9d3af9",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 218, 182, 138, 185, 184, 172, 9, 20, 148, 103, 3, 183, 225, 5, 113, 123, 115, 2, 150, 15, 110, 247, 234, 0, 165, 132, 159, 190, 28, 99, 180, 213, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}