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: a019397e3a251dc016363c67685d85d371f15af9d274f978efd2c9003cc0315e
Tx prefix hash: 6bf020659f9ddf1dcdefd82b961705c6daab832cd55f3933e92f4f07f9bd6ae7
Tx public key: f1a7be7557c31a8ce79691cd940a374a69f812d4dab98e25abe4f5cda8f7d920
| Timestamp: 1780042183 | Timestamp [UTC]: 2026-05-29 08:09:43 | Age [y:d:h:m:s]: 00:010:17:26:14 |
| Block: 4301 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3585 | RingCT/type: yes/0 |
| Extra: 01f1a7be7557c31a8ce79691cd940a374a69f812d4dab98e25abe4f5cda8f7d92002090000000426697be300 | ||
1 output(s) for total of 34.896983832266 HMNY
| stealth address | amount | amount idx | tag |
| 00: f863488c343efea87984a9151bf4b078f3bf2f044b285aabc48888f3e4803252 | 34.896983832266 | 5375 of 0 | <17> |
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": 4361,
"vin": [ {
"gen": {
"height": 4301
}
}
],
"vout": [ {
"amount": 34896983832266,
"target": {
"tagged_key": {
"key": "f863488c343efea87984a9151bf4b078f3bf2f044b285aabc48888f3e4803252",
"view_tag": "17"
}
}
}
],
"extra": [ 1, 241, 167, 190, 117, 87, 195, 26, 140, 231, 150, 145, 205, 148, 10, 55, 74, 105, 248, 18, 212, 218, 185, 142, 37, 171, 228, 245, 205, 168, 247, 217, 32, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}