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: 3f0e9646d13fe0416395d76fd34210583a3b44d90f4153e40f0ef86f5558104b
Tx prefix hash: d2f5eaefd8d8dd79875830cd1622b58976b439b16d3af85ea7403096c644db99
Tx public key: 79db1b8e52cf3f158550fe966de29171cda23cf79a0760d127fcf0f2ad90c2b8
| Timestamp: 1779716060 | Timestamp [UTC]: 2026-05-25 13:34:20 | Age [y:d:h:m:s]: 00:014:12:01:37 |
| Block: 1647 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6239 | RingCT/type: yes/0 |
| Extra: 0179db1b8e52cf3f158550fe966de29171cda23cf79a0760d127fcf0f2ad90c2b8020900000001ba6d17be00 | ||
1 output(s) for total of 35.074084008694 HMNY
| stealth address | amount | amount idx | tag |
| 00: d16b5ec838543c18d81aa1d61f464aa80263f86933e520d8fba253043d96b5e1 | 35.074084008694 | 1809 of 0 | <fa> |
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": 1707,
"vin": [ {
"gen": {
"height": 1647
}
}
],
"vout": [ {
"amount": 35074084008694,
"target": {
"tagged_key": {
"key": "d16b5ec838543c18d81aa1d61f464aa80263f86933e520d8fba253043d96b5e1",
"view_tag": "fa"
}
}
}
],
"extra": [ 1, 121, 219, 27, 142, 82, 207, 63, 21, 133, 80, 254, 150, 109, 226, 145, 113, 205, 162, 60, 247, 154, 7, 96, 209, 39, 252, 240, 242, 173, 144, 194, 184, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}