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: 05c16523eb1e08835afe79a5e96849975fb16f4ee77ebe08387a688b1510d7de
Tx prefix hash: e72aa3bc9cf64bb0a1f6ca3259a1968b515dbb72cde61a48a966d11f95cdaf2b
Tx public key: 640279772ef3946f2eac06e044cad1691d4f9df1ce46bcc469e1a0ea278d4d80
| Timestamp: 1779796592 | Timestamp [UTC]: 2026-05-26 11:56:32 | Age [y:d:h:m:s]: 00:013:13:39:25 |
| Block: 2272 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5614 | RingCT/type: yes/0 |
| Extra: 01640279772ef3946f2eac06e044cad1691d4f9df1ce46bcc469e1a0ea278d4d8002090000000326697be300 | ||
1 output(s) for total of 35.032297314240 HMNY
| stealth address | amount | amount idx | tag |
| 00: ae50ca46e677b01dfab66560fbb4c1e3e124b215f324c37c73067275b469ddc3 | 35.032297314240 | 2642 of 0 | <1e> |
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": 2332,
"vin": [ {
"gen": {
"height": 2272
}
}
],
"vout": [ {
"amount": 35032297314240,
"target": {
"tagged_key": {
"key": "ae50ca46e677b01dfab66560fbb4c1e3e124b215f324c37c73067275b469ddc3",
"view_tag": "1e"
}
}
}
],
"extra": [ 1, 100, 2, 121, 119, 46, 243, 148, 111, 46, 172, 6, 224, 68, 202, 209, 105, 29, 79, 157, 241, 206, 70, 188, 196, 105, 225, 160, 234, 39, 141, 77, 128, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}