← previous blocknext block →recent activity
Analyzing
Block #95,796,511
22 transactions · 21 stateful · 2026-08-14 02:20:44 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
1.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,796,511 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w18w29w210w311w112w213w317w418w419w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8075c973…5011
0x34b655…2a6f
10 touches
10 conflicts
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0x8a02d049…f481
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
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: Perpl
10 conflicts on slot 0x8075c97307…e85011
Audit this contract →
← previous block·next block →recent activity