← previous blocknext block →recent activity

Analyzing

Block #87,319,041

18 transactions · 18 stateful · 2026-07-12 18:00:42 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,319,041  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x5f60e4d7…8ce3

0x34b655…2a6f

4 touches
1 conflict

0x6e1cd42e…1f23

0x34b655…2a6f

4 touches
1 conflict

0x75ac5fa0…1808

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4ab

0x34b655…2a6f

4 touches
1 conflict

0x94ba9c4a…41d8

0x34b655…2a6f

4 touches
1 conflict

0x954aad92…7358

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 0x0000000000…00003d

← previous block·next block →recent activity