Flap Dividend Claim
*
The payer submits contract calls and pays fees. Dividends go directly to each row’s recipient.
The recipient must own the dividend entitlement. Another holder’s rewards cannot be redirected.
# | Token | Tax information | Recipient address | Pending dividends | Status | Actions | |
|---|---|---|---|---|---|---|---|
| Enter token and recipient addresses, or import an address list for the selected modes. | |||||||
The first 10 rows are checked initially. Starting the task checks the remaining rows in groups of 10 and sends bundles of up to 20 transactions.
This tab saves task progress but never your private key. Enter the same payer wallet private key when you return to check or continue your task.
Total cost
Imported rows
0
Checked rows
0
Claimable
0
Skipped rows
0
Rows with errors
0
Bundles
0
Service fee
Complete inputs for automatic estimation
Service fee per row: 0.00008 BNB
Estimated Gas
Complete inputs for automatic estimation
Estimated total cost
Complete inputs for automatic estimation
Payer balance
--
The current estimate includes only checked, claimable rows and is not the final cost of the whole list. Gas, service fees and the payer balance are checked again before each bundle is sent. Service fees apply per executed row. Network Gas still applies when the service fee is 0; final Gas depends on on-chain usage.
The lowest service fee in the network, only per address
0.00008
0.0001 BNBBatch claim Flap dividends for yourself or other holders. Token and recipient addresses each support shared and per-row modes; the default uses one token and multiple recipients. Two shared addresses create one row automatically; other combinations accept pasted Excel data or address files. The first 10 rows are checked initially, and the estimate covers only checked, claimable rows. Starting the task checks the rest in groups and sends bundles of up to 20 claims. Rewards belong to each specified recipient; the payer covers Gas and the displayed service fee.
How to Use
- Enter the payer private key. This wallet submits contract calls and pays network fees in BNB.
- Choose token and recipient modes separately. Enter a shared token once. Confirm a shared recipient below the list; both entries must be valid and match before queries begin. Recipient fields can use the connected wallet.
- For one shared token, import one recipient-address column. For one shared recipient, import one token-address column. When both vary, import token-address and recipient-address columns. Two shared addresses need no import. Identical token and recipient pairs are deduplicated without regard to case, keeping the first row.
- Complete the settings to check the first 10 rows. Review taxes, pending rewards and status. Expanding Details loads cumulative dividends, holdings and thresholds. Remaining rows wait for checks; the entire list does not need to finish querying first.
- Review the estimate for checked rows and start the task. Rows are checked in groups of 10, and claimable rows are sent in bundles of up to 20. Before each send, claims are simulated again and Gas, service fees and the payer balance are checked. Processing continues after the preceding bundle is confirmed.
- Review row statuses and explorer links. A failed row does not stop other claimable rows; hover over its status for the reason. Resolve funding, network or unknown-transaction issues before continuing.
Need support for Flap Dividend Claim? contact us.
FAQ
What does Dividend Claim do?
It uses official Flap contracts to batch claim accumulated token dividends for specified holders. The payer submits transactions and pays fees; on-chain contracts determine claim results.
How can tokens and recipients be configured?
The two mode switches work independently: one token with many recipients, many tokens with one recipient, one token-recipient pair per row, or a single token for a single recipient. Two shared addresses create one row automatically. A shared recipient must still be entered twice for confirmation.
Can I redirect another holder’s dividends to my address?
No. The recipient must own the dividend entitlement. Claiming for another holder only submits the transaction on their behalf; the rewards remain payable to their entitled address.
Why do only some imported rows have query results?
Only the first 10 rows are checked initially. Starting the task checks remaining rows in groups of 10. A larger list can continue even if its first group has no claimable rewards. The estimate covers only checked, claimable rows and is not the final cost of the entire list.
How many claims can I submit?
There is no fixed row-count limit. Rows are checked in groups and sent in bundles of up to 20 claims. Each bundle confirms independently, so later failures do not reverse earlier confirmed bundles.
What happens if the balance is insufficient?
Before each send, the page checks claim Gas for that bundle, accrued service fees and fee-transaction Gas. Insufficient funding stops that bundle; fund the payer to continue unfinished work. The initial estimate does not guarantee enough funds for the whole list. Confirmed transactions retain their results, and expected dividends do not reduce the required BNB balance.
Which asset will recipients receive?
Dividends are paid in the reward asset configured by the token’s dividend contract. WBNB rewards request unwrapping to BNB; other reward tokens are paid as their original asset. The contract execution result is final.
How are fees charged?
Service fees use the transfer tool’s per-address pricing. The displayed rate applies to each executed token-recipient row. BSC network Gas still applies when the service fee is 0. A positive service fee is collected by the last transaction in the final bundle. If only the fee remains, that transaction is sent in a separate final bundle.