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: 2c83d61ec648bccb0412ebb35d88507e5cbfda802b6d46b67736669b0f0c0b8d
Tx prefix hash: 4e4f387ca3d870feb8d70c38315643ca47f8231981eaaeac59f305e76b501c06
Tx public key: 9292a5b3df53f872dd6ff1a417ab51c341b1f0185c6c4133b27e5c194a3a2c09
| Timestamp: 1779884844 | Timestamp [UTC]: 2026-05-27 12:27:24 | Age [y:d:h:m:s]: 00:018:19:52:11 |
| Block: 3000 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5745 | RingCT/type: yes/0 |
| Extra: 019292a5b3df53f872dd6ff1a417ab51c341b1f0185c6c4133b27e5c194a3a2c0902090000000226697be300 | ||
1 output(s) for total of 34.983686935064 HMNY
| stealth address | amount | amount idx | tag |
| 00: 75ca412c241fb044e32a2c4ce394862e858e385a0cfea831c085dace7550936c | 34.983686935064 | 3560 of 0 | <2a> |
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": 3060,
"vin": [ {
"gen": {
"height": 3000
}
}
],
"vout": [ {
"amount": 34983686935064,
"target": {
"tagged_key": {
"key": "75ca412c241fb044e32a2c4ce394862e858e385a0cfea831c085dace7550936c",
"view_tag": "2a"
}
}
}
],
"extra": [ 1, 146, 146, 165, 179, 223, 83, 248, 114, 221, 111, 241, 164, 23, 171, 81, 195, 65, 177, 240, 24, 92, 108, 65, 51, 178, 126, 92, 25, 74, 58, 44, 9, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}