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: 7d8b0045ea2913392e09e1b6fb6bd6ebc0b113d74acf47977a7e3922eb4b0b5b
Tx prefix hash: bedf36c3acbebad6e05992f1def383cc38c722427fe327731ff3e6f900861e19
Tx public key: a1cc2af37bf01c3f5388afc708ba1765928c1b2800f2234bd0e1b9a3caaf176f
| Timestamp: 1781002480 | Timestamp [UTC]: 2026-06-09 10:54:40 | Age [y:d:h:m:s]: 00:007:22:20:26 |
| Block: 8478 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 267 | RingCT/type: yes/0 |
| Extra: 01a1cc2af37bf01c3f5388afc708ba1765928c1b2800f2234bd0e1b9a3caaf176f020900000001e49593ff00 | ||
1 output(s) for total of 34.620064038203 HMNY
| stealth address | amount | amount idx | tag |
| 00: 81a727597250b414813f331418140f01e3571c803e4645bc7b20347dbb16633e | 34.620064038203 | 10474 of 0 | <ad> |
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": 8538,
"vin": [ {
"gen": {
"height": 8478
}
}
],
"vout": [ {
"amount": 34620064038203,
"target": {
"tagged_key": {
"key": "81a727597250b414813f331418140f01e3571c803e4645bc7b20347dbb16633e",
"view_tag": "ad"
}
}
}
],
"extra": [ 1, 161, 204, 42, 243, 123, 240, 28, 63, 83, 136, 175, 199, 8, 186, 23, 101, 146, 140, 27, 40, 0, 242, 35, 75, 208, 225, 185, 163, 202, 175, 23, 111, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}