← previous blocknext block →recent activity

Analyzing

Block #95,111,866

13 transactions · 12 stateful · 2026-08-11 16:42:31 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,111,866  ·  13 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

0x3de775b2…319b

0xa6afd3…d132

4 touches
1 conflict

0x5f72d58f…c445

0x34b655…2a6f

4 touches
1 conflict

0x745952b2…d90c

0x34b655…2a6f

4 touches
1 conflict

0xa07e7b13…7513

0x34b655…2a6f

4 touches
1 conflict

0xb42343e0…2a28

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd7d3e7dd…2bf3

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

1 conflict on slot 0x3de775b20f…f1319b

← previous block·next block →recent activity