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: 07464bc90773bf2c8cc95ad08af9ee5d659b217df996a04379ff3d041d7463ef
Tx prefix hash: da620c315ce6418ebac56569fd3470829bdd94dadc99931a1fcbef346f22e58d
Tx public key: de0e6dceeb763b688fcb2c4b092c3f7292a9662d4e7e56ec2406279454876e30
| Timestamp: 1779862885 | Timestamp [UTC]: 2026-05-27 06:21:25 | Age [y:d:h:m:s]: 00:021:01:43:56 |
| Block: 2705 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6040 | RingCT/type: yes/0 |
| Extra: 01de0e6dceeb763b688fcb2c4b092c3f7292a9662d4e7e56ec2406279454876e3002090000000326697be300 | ||
1 output(s) for total of 35.003376688515 HMNY
| stealth address | amount | amount idx | tag |
| 00: a28a4c1995feeecc0c70b847446c3fafcb332c77a0354fddef70af33d9115d8e | 35.003376688515 | 3193 of 0 | <e1> |
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": 2765,
"vin": [ {
"gen": {
"height": 2705
}
}
],
"vout": [ {
"amount": 35003376688515,
"target": {
"tagged_key": {
"key": "a28a4c1995feeecc0c70b847446c3fafcb332c77a0354fddef70af33d9115d8e",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 222, 14, 109, 206, 235, 118, 59, 104, 143, 203, 44, 75, 9, 44, 63, 114, 146, 169, 102, 45, 78, 126, 86, 236, 36, 6, 39, 148, 84, 135, 110, 48, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}