← previous blocknext block →recent activity

Analyzing

Block #95,122,398

23 transactions · 21 stateful · 2026-08-11 17:35:29 UTC

Parallelism

83/100

Blocked

38%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,122,398  ·  23 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

0xfa551be3…a911

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xa56e54d0…2d39

0x34b655…2a6f

6 touches
3 conflicts

0x2021fb2a…d63b

0x34b655…2a6f

4 touches
1 conflict

0x2021fb2a…d63c

0x34b655…2a6f

4 touches
1 conflict

0x2385516f…eca5

0x34b655…2a6f

4 touches
1 conflict

0x2592d715…a50e

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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 0xfa551be3e9…caa911

← previous block·next block →recent activity