← previous blocknext block →recent activity
Analyzing
Block #95,782,915
29 transactions · 26 stateful · 2026-08-14 01:12:22 UTC
Parallelism
76/100
Blocked
46%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,782,915 · 29 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w210w311w413w514w615w618w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c7064fa…682d
0x34b655…2a6f
12 touches
15 conflicts
0x4efae872…6aa8
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x1fa581e1…53d8
0x34b655…2a6f
9 touches
10 conflicts
0x5b6af007…0f35
0x34b655…2a6f
8 touches
6 conflicts
0x7e95fe64…7024
0x851145…3f07
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
15 conflicts on slot 0x2c7064fa7c…38682d
Audit this contract →
← previous block·next block →recent activity