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: ee1db5fda63ed54f5a75639dc6adc7c0d53195d2edb0ade3266544c74b6b9dad
Tx prefix hash: 889c91f11069f7d27e18723effbd1ba10e6fd874f38d48a2aee17678bebc4ac4
Tx public key: 6749cb8f4bb4bf9c47bac944b4a21c0c98e910713e38c20406b4606bf9ee01a9
| Timestamp: 1779720102 | Timestamp [UTC]: 2026-05-25 14:41:42 | Age [y:d:h:m:s]: 00:014:10:54:15 |
| Block: 1741 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6145 | RingCT/type: yes/0 |
| Extra: 016749cb8f4bb4bf9c47bac944b4a21c0c98e910713e38c20406b4606bf9ee01a9020900000001ba6d17be00 | ||
1 output(s) for total of 35.067796106815 HMNY
| stealth address | amount | amount idx | tag |
| 00: af19c43d22e74eddf48db658f13bd7fc93cee54af62e986bddb72987e70a95e2 | 35.067796106815 | 1919 of 0 | <3f> |
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": 1801,
"vin": [ {
"gen": {
"height": 1741
}
}
],
"vout": [ {
"amount": 35067796106815,
"target": {
"tagged_key": {
"key": "af19c43d22e74eddf48db658f13bd7fc93cee54af62e986bddb72987e70a95e2",
"view_tag": "3f"
}
}
}
],
"extra": [ 1, 103, 73, 203, 143, 75, 180, 191, 156, 71, 186, 201, 68, 180, 162, 28, 12, 152, 233, 16, 113, 62, 56, 194, 4, 6, 180, 96, 107, 249, 238, 1, 169, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}