← previous blocknext block →recent activity

Analyzing

Block #87,054,929

16 transactions · 15 stateful · 2026-07-11 12:34:40 UTC

Parallelism

75/100

Blocked

53%

Avg conflicts / tx

0.81

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,054,929  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x17c44db3…8888

0xa6afd3…d132

8 touches
6 conflicts

0xbcc5ae85…6ba2

0xa6afd3…d132

8 touches
6 conflicts

0x7dc98782…f193

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x93ffcd76…894e

0x34b655…2a6f

4 touches
1 conflict

0xa57576bb…e01f

0x34b655…2a6f

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Kuru Exchange: Market-WETH/USDC

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity