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: 1d6825f0442f30fdbdcd814107fdc46a83526cc04515747b03575ed000a70e1e
Tx prefix hash: 58f21ee6b363e662b4ecb485f828dced1b84be7c698140b9a224e1668a193888
Tx public key: 7661f99cac4fd4a9d587ae098672e9d6cc46d2fa6038d5f7f425f31b3b526a44
| Timestamp: 1779463882 | Timestamp [UTC]: 2026-05-22 15:31:22 | Age [y:d:h:m:s]: 00:017:11:18:26 |
| Block: 483 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7437 | RingCT/type: yes/0 |
| Extra: 017661f99cac4fd4a9d587ae098672e9d6cc46d2fa6038d5f7f425f31b3b526a4402090000000293369e7d00 | ||
1 output(s) for total of 35.152040449858 HMNY
| stealth address | amount | amount idx | tag |
| 00: acf311286d29f810228bd41a58cc16f3ce98fb8854540cc3d81f09905835836e | 35.152040449858 | 487 of 0 | <a5> |
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": 543,
"vin": [ {
"gen": {
"height": 483
}
}
],
"vout": [ {
"amount": 35152040449858,
"target": {
"tagged_key": {
"key": "acf311286d29f810228bd41a58cc16f3ce98fb8854540cc3d81f09905835836e",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 118, 97, 249, 156, 172, 79, 212, 169, 213, 135, 174, 9, 134, 114, 233, 214, 204, 70, 210, 250, 96, 56, 213, 247, 244, 37, 243, 27, 59, 82, 106, 68, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}