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: da2a761aed082db1be84bb5622e13e43d8e51d40cbe8265bfc715a267f92c4da
Tx prefix hash: c4a2bdd4f08ed5770da824974e65e3267b0c3d6ebecc78a333f4c4a0c00d822d
Tx public key: 5ca9967e2ebf27a0a90c264ae76bd614a11d3fb823bcdb5a241728d6343d1f98
| Timestamp: 1779942033 | Timestamp [UTC]: 2026-05-28 04:20:33 | Age [y:d:h:m:s]: 00:020:04:01:46 |
| Block: 3511 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5234 | RingCT/type: yes/0 |
| Extra: 015ca9967e2ebf27a0a90c264ae76bd614a11d3fb823bcdb5a241728d6343d1f9802090000000226697be300 | ||
1 output(s) for total of 34.949606482920 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9e1d3b1ea200414334b0e820bb1c7d9ca2a52c22bee9f1b26edf6d550192a2a4 | 34.949606482920 | 4235 of 0 | <b5> |
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": 3571,
"vin": [ {
"gen": {
"height": 3511
}
}
],
"vout": [ {
"amount": 34949606482920,
"target": {
"tagged_key": {
"key": "9e1d3b1ea200414334b0e820bb1c7d9ca2a52c22bee9f1b26edf6d550192a2a4",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 92, 169, 150, 126, 46, 191, 39, 160, 169, 12, 38, 74, 231, 107, 214, 20, 161, 29, 63, 184, 35, 188, 219, 90, 36, 23, 40, 214, 52, 61, 31, 152, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}