← previous blocknext block →recent activity
Analyzing
Block #95,369,828
21 transactions · 16 stateful · 2026-08-12 14:31:52 UTC
Parallelism
62/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,369,828 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w29w310w417w518w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
10 touches
10 conflicts
0xfb53ecf8…bd11
0x34b655…2a6f
8 touches
6 conflicts
0x8ab258fd…32af
0x34b655…2a6f
6 touches
3 conflicts
0x3bab4355…fbfd
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity