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: 08b19c7fdfdde1f9fc9733ccc2433317be2c1b555926beb000c2b98865f0ac8d
Tx prefix hash: 9a33d3459b9c1e7fa359807be4320f3f597a809aa7dc3249c6fdd2feaf32d4c3
Tx public key: aea4b314bd2406c4d902a8a5a404ceaaf71a660028e69da130358f261c3cd25d
| Timestamp: 1779928949 | Timestamp [UTC]: 2026-05-28 00:42:29 | Age [y:d:h:m:s]: 00:012:02:07:19 |
| Block: 3391 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4529 | RingCT/type: yes/0 |
| Extra: 01aea4b314bd2406c4d902a8a5a404ceaaf71a660028e69da130358f261c3cd25d02090000000126697be300 | ||
1 output(s) for total of 34.960216736168 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3989c0a89af3cc40b277400dc82d418b6545874be0e20a36d0a80abfd4e760d4 | 34.960216736168 | 4098 of 0 | <46> |
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": 3451,
"vin": [ {
"gen": {
"height": 3391
}
}
],
"vout": [ {
"amount": 34960216736168,
"target": {
"tagged_key": {
"key": "3989c0a89af3cc40b277400dc82d418b6545874be0e20a36d0a80abfd4e760d4",
"view_tag": "46"
}
}
}
],
"extra": [ 1, 174, 164, 179, 20, 189, 36, 6, 196, 217, 2, 168, 165, 164, 4, 206, 170, 247, 26, 102, 0, 40, 230, 157, 161, 48, 53, 143, 38, 28, 60, 210, 93, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}