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: ee5223e42ca3c0a4ad1ce2bba3eddc1400ef71be5a536de389699960d132dc53
Tx prefix hash: 31f1ea0524ee7799d0bf6a760f644a1fa7290c533604b6ea009a2435cbe78caf
Tx public key: 42b1d1ec9d69db8f4850370806386cdf0f2cc5581e0107fb41b89ba8e3388294
| Timestamp: 1779967624 | Timestamp [UTC]: 2026-05-28 11:27:04 | Age [y:d:h:m:s]: 00:011:15:13:32 |
| Block: 3823 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4074 | RingCT/type: yes/0 |
| Extra: 0142b1d1ec9d69db8f4850370806386cdf0f2cc5581e0107fb41b89ba8e338829402090000000a26697be300 | ||
1 output(s) for total of 34.928814392063 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4df80eac483a5ce308a665da00e90851e8dfd075e2f7141898af3b730c0a1452 | 34.928814392063 | 4655 of 0 | <e2> |
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": 3883,
"vin": [ {
"gen": {
"height": 3823
}
}
],
"vout": [ {
"amount": 34928814392063,
"target": {
"tagged_key": {
"key": "4df80eac483a5ce308a665da00e90851e8dfd075e2f7141898af3b730c0a1452",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 66, 177, 209, 236, 157, 105, 219, 143, 72, 80, 55, 8, 6, 56, 108, 223, 15, 44, 197, 88, 30, 1, 7, 251, 65, 184, 155, 168, 227, 56, 130, 148, 2, 9, 0, 0, 0, 10, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}