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: aa8f60e750e8fff4a22ff38251c21972c91609740bc71803391ec424d7e4e5c8
Tx prefix hash: 264106e555444a16ed3d917781671e4120799102bdf0df99f618387ab3c06a52
Tx public key: d3bef5350c6ee314bc1fe5e6699a39f4e044779a0b2ac212e7ebac02784258e4
| Timestamp: 1780855054 | Timestamp [UTC]: 2026-06-07 17:57:34 | Age [y:d:h:m:s]: 00:001:06:49:13 |
| Block: 7564 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 322 | RingCT/type: yes/0 |
| Extra: 01d3bef5350c6ee314bc1fe5e6699a39f4e044779a0b2ac212e7ebac02784258e4020900000001e49593ff00 | ||
1 output(s) for total of 34.680470468356 HMNY
| stealth address | amount | amount idx | tag |
| 00: 182e5e3c043684a7ba997804ed5746480fe03b23b60326fc2f592e7fc5f89cab | 34.680470468356 | 9340 of 0 | <67> |
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": 7624,
"vin": [ {
"gen": {
"height": 7564
}
}
],
"vout": [ {
"amount": 34680470468356,
"target": {
"tagged_key": {
"key": "182e5e3c043684a7ba997804ed5746480fe03b23b60326fc2f592e7fc5f89cab",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 211, 190, 245, 53, 12, 110, 227, 20, 188, 31, 229, 230, 105, 154, 57, 244, 224, 68, 119, 154, 11, 42, 194, 18, 231, 235, 172, 2, 120, 66, 88, 228, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}