← previous blocknext block →recent activity
Analyzing
Block #95,382,256
53 transactions · 44 stateful · 2026-08-12 15:34:52 UTC
Parallelism
68/100
Blocked
70%
Avg conflicts / tx
1.55
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #95,382,256 · 53 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w18w111w012w113w214w215w316w417w518w624w225w731w337w139w542w243w1045w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xce06a0f7…efef
0x34b655…2a6f
10 touches
10 conflicts
0x0bf3a8e0…ddef
0x34b655…2a6f
10 touches
10 conflicts
0x81561f70…fefd
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity