← previous blocknext block →recent activity

Analyzing

Block #95,758,056

22 transactions · 20 stateful · 2026-08-13 23:07:20 UTC

Parallelism

77/100

Blocked

35%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,758,056  ·  22 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

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x0cc65720…396c

0x34b655…2a6f

6 touches
3 conflicts

0x6000a31d…f851

0x065c9d…c394

6 touches
3 conflicts

0x0778475b…bd75

0x2a68ba…90c5

6 touches
3 conflicts

0x5347d954…ce37

0x34b655…2a6f

4 touches
1 conflict

0x5484fc7f…a8d8

0x34b655…2a6f

4 touches
1 conflict

0x6f1a10f8…5a04

0x34b655…2a6f

4 touches
1 conflict

0x7a821847…15b0

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: USDC (USDC)

10 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity