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: f3f9c568d847c089cf439a90e5a03111bc3be338c919e417a7a7e3d247742919
Tx prefix hash: 41691929b813f701e96011a9b8bcf91f0ecb0e5852657fb33c8c87b37a463052
Tx public key: b4f944fb05e8f1af58b3f91a05637396fbe08a326e00a425e34a1e1b05cd3ec0
| Timestamp: 1779798918 | Timestamp [UTC]: 2026-05-26 12:35:18 | Age [y:d:h:m:s]: 00:013:13:00:39 |
| Block: 2287 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5599 | RingCT/type: yes/0 |
| Extra: 01b4f944fb05e8f1af58b3f91a05637396fbe08a326e00a425e34a1e1b05cd3ec002090000000126697be300 | ||
1 output(s) for total of 35.031295045556 HMNY
| stealth address | amount | amount idx | tag |
| 00: de5ba6298a15d0ec2b935d4cb049807e2cef8103ef45e41e43d2656874b86ed6 | 35.031295045556 | 2665 of 0 | <49> |
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": 2347,
"vin": [ {
"gen": {
"height": 2287
}
}
],
"vout": [ {
"amount": 35031295045556,
"target": {
"tagged_key": {
"key": "de5ba6298a15d0ec2b935d4cb049807e2cef8103ef45e41e43d2656874b86ed6",
"view_tag": "49"
}
}
}
],
"extra": [ 1, 180, 249, 68, 251, 5, 232, 241, 175, 88, 179, 249, 26, 5, 99, 115, 150, 251, 224, 138, 50, 110, 0, 164, 37, 227, 74, 30, 27, 5, 205, 62, 192, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}