← previous blocknext block →recent activity

Analyzing

Block #87,254,259

18 transactions · 14 stateful · 2026-07-12 10:47:34 UTC

Parallelism

72/100

Blocked

64%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,254,259  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x17c44db3…8888

0xa6afd3…d132

6 touches
3 conflicts

0xe2307994…acad

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xbcc5ae85…6ba2

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x3b9bb58c…e73a

0x34b655…2a6f

4 touches
1 conflict

0x43ffd8bd…0d0c

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

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

3 conflicts on slot 0x17c44db3e4…ef8888

← previous block·next block →recent activity