$哥布林 — 10% comes back

Market board

哥$哥布林V3—0x5b78…7777 · StockGoblin10%COMES BACK

Grade

Buy / Sell

3% / 3%

To holders

10%

Paid in

—

Mkt cap

4.50 BNB

Price

4.50e-9 BNB

Status

DEX

Paid total

0.000 BNB

Minimum

10,000

Curve

DEX

What you actually get

live from chain

Holding $哥布林 pays you in payout tokens, pushed to your wallet as trades happen. You are only paid while you hold at least — 哥布林 — below that you receive nothing at all, however long you hold.

You receive

—

The payout token's symbol could not be read.

To qualify, hold

—

The gate is 10000000000000000000000 base units, but this token's decimals() could not be read, so it cannot be shown in whole tokens.

Pays about

once so far

One payout on record — not enough history to state a rhythm.

Last payout

2.2 days ago

0.0001683 payout tokens paid across 1 dispatch on record.

Every buy pays 3% tax and every sell 3%. That is charged on the trade, not on your balance — holding costs nothing.
None of that tax is routed to holders: 0% goes to a dividend contract and the marketing wallet is not a registered vault.
Only wallets holding at least — 哥布林 are credited. minimumShareBalance is enforced by the contract, not by policy.

Where the tax actually goes10% back · 90% out

DividendNothing routed here.0%

LiquidityAdded to the pool. Not paid to you, but it deepens the book you eventually sell into.10%

BurnNothing routed here.0%

TeamLeaves to a plain wallet. Nothing on-chain constrains what happens to it.90%

Percentages are shares of the tax remaining after Flap’s protocol fee, read from getTaxTokenInfoV2. They sum to 100%. The marketing bucket is labelled as extraction because the marketing wallet is a plain address with no vault contract behind it — nothing on-chain says what happens to it next.

Payout record1 dispatch

Dispatches

Total paid

0.0001683 payout tokens

Average each

0.0001683 payout tokens

Median gap

—

Longest gap

—

Since last

2.2 days

Observed over

Counted from 1 Transfer log of payout tokens out of this token’s vault, tax processor or the token itself, grouped by transaction — one transaction can carry several transfers (a vault flushing a few accrued batches at once), and a holder experienced that as one moment of being paid, not several. Amounts are counted in payout tokens and scaled by that token’s own decimals() — the unit is the payout asset itself, never a converted currency.

The median and the longest gap are both shown because this stream is bursty: quoting either one alone would misdescribe it. Payouts follow trading activity — tax accrues, and it is dispatched when it accrues, not on a clock.

This covers only the blocks scanned so far, not all history. Coverage is extended a little further into the past on every visit, so these totals can only grow — treat them as a floor, never as a lifetime total.

What you actually get

reading vault

Dividend dispatched

Dispatchednone

Cumulative0

Paid to holders (tokens)Cumulativebars = dispatch events, not a smooth flow

Dividend dispatched

reading chain

Scanning for payouts…

Where the tax goes

bps of remainder

Dividend~~0 bps~~0%

Liquidity~~1000 bps~~10%

Burn~~0 bps~~0%

Team~~9000 bps~~90%

Breaks the payback1

90% leaves to the team

marketBps 9000 goes to the marketing wallet — a plain EOA with nothing constraining it. Funding a team isn't wrong, but only 10% is pointed at holders.

Working for you1

10% deepens the pool

lpBps 1000 is added to liquidity on each dispatch. It never hits your wallet, but it cuts the slippage you pay to exit.

Worth knowing1

No direct dividend

dividendBps 0. The dividend contract exists and tracks your share, but no tax routes to it, and no vault is in the path either. Any return has to come from price.