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: 827b7a2852f201ab0300b81511a7f4c4f7f70cc395b1d6163622fcf4c49ea253
Tx prefix hash: cc14d15716bf042dc2b429cdf2d35188e9ac7f955d9b3a2a4986a4318fa3a168
Tx public key: 72b58543b99fb29e0e1ec8c5942b2e06f03929c158f606ff5b71cbe5150c75f6
| Timestamp: 1779854874 | Timestamp [UTC]: 2026-05-27 04:07:54 | Age [y:d:h:m:s]: 00:012:23:30:56 |
| Block: 2603 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5347 | RingCT/type: yes/0 |
| Extra: 0172b58543b99fb29e0e1ec8c5942b2e06f03929c158f606ff5b71cbe5150c75f602090000000126697be300 | ||
1 output(s) for total of 35.010187249036 HMNY
| stealth address | amount | amount idx | tag |
| 00: c75fc106323d7da98748a47100fb79e897e5e39099cfbb7c48e409d4256b494f | 35.010187249036 | 3063 of 0 | <47> |
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": 2663,
"vin": [ {
"gen": {
"height": 2603
}
}
],
"vout": [ {
"amount": 35010187249036,
"target": {
"tagged_key": {
"key": "c75fc106323d7da98748a47100fb79e897e5e39099cfbb7c48e409d4256b494f",
"view_tag": "47"
}
}
}
],
"extra": [ 1, 114, 181, 133, 67, 185, 159, 178, 158, 14, 30, 200, 197, 148, 43, 46, 6, 240, 57, 41, 193, 88, 246, 6, 255, 91, 113, 203, 229, 21, 12, 117, 246, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}