Backrun Shield

What the endpoint has handled.

Everything here comes from the endpoint's own records. There is no account to create and no wallet to connect — look up an address the way you would on an explorer.

Totals
Swaps protected—
Wallets that sent a swap—
Refunds paid—
Transactions protected, all kinds—
Included privately—
Sending addresses, all kinds—

Loading…

Since 20 October most transactions here are transfers from one automated sweep, so the honest measure of people using the endpoint is the swaps and the wallets that sent one, shown first. Sending addresses counts every address that sent a transaction here, people, payment services and automated senders alike. A transaction that is never included is usually a copy its sender also sent elsewhere, which landed first.

Look up an address

What has this wallet sent?

We answer for one address at a time and never publish the list of users. The same figures are available as JSON at /stats?address=0x….

Rebates

Who got paid.

When a backrun of ours lands behind a transaction sent here, 60 % of that backrun's profit after gas is credited to the address that signed the transaction, never more than the backrun itself netted after the builder's bid. A wallet, bot or app that sends its users' transactions through its own link, https://rpc.backrunshield.com/r/<its address>, is paid that share for its flow instead. Payment is automatic: every hour, in BNB, from the rebate wallet 0xD465…Cce57, as soon as an address is owed a cent, after a sanctions screen. The rows below are that wallet's own transfers on the chain; follow any of them.

Backruns behind transactions sent here—
Paid out—
Owed, not yet paid—
Loading…

Amounts are shown to the cent of a cent: a backrun behind a small swap earns little, and the table says so rather than rounding it up. "Owed, not yet paid" is what the hourly run will pay next.