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: 422f8076cec9510c7b18184442108fa4d7d81004e11bcebb6cbb8cbd7dfba497
Tx prefix hash: 200f14ca0759317e1b3563f9936c0a240e4a4825dff5062755427a4c20734378
Tx public key: 394a11e8e7256bd9265cc6330d78f46d79d1efa773fe4588ff7a1d8f7b443734
| Timestamp: 1780981053 | Timestamp [UTC]: 2026-06-09 04:57:33 | Age [y:d:h:m:s]: 00:000:08:40:03 |
| Block: 8030 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 568 | RingCT/type: yes/0 |
| Extra: 01394a11e8e7256bd9265cc6330d78f46d79d1efa773fe4588ff7a1d8f7b443734020900000001e49593ff00 | ||
1 output(s) for total of 34.649659283331 HMNY
| stealth address | amount | amount idx | tag |
| 00: 98abbc420306ba2b2bb583fdf904454c3382836e33eeac326f0266097c822626 | 34.649659283331 | 9954 of 0 | <7c> |
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": 8090,
"vin": [ {
"gen": {
"height": 8030
}
}
],
"vout": [ {
"amount": 34649659283331,
"target": {
"tagged_key": {
"key": "98abbc420306ba2b2bb583fdf904454c3382836e33eeac326f0266097c822626",
"view_tag": "7c"
}
}
}
],
"extra": [ 1, 57, 74, 17, 232, 231, 37, 107, 217, 38, 92, 198, 51, 13, 120, 244, 109, 121, 209, 239, 167, 115, 254, 69, 136, 255, 122, 29, 143, 123, 68, 55, 52, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}