← previous blocknext block →recent activity
Analyzing
Block #95,782,759
31 transactions · 25 stateful · 2026-08-14 01:11:35 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.03
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #95,782,759 · 31 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w29w010w011w112w113w214w315w018w419w524w725w128w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
8 touches
6 conflicts
0xbf99cee5…73cd
0x34b655…2a6f
6 touches
3 conflicts
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0x4696620e…722d
0xd32edf…ff58
5 touches
3 conflicts
0x69ee34d1…30f8
0x34b655…2a6f
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
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: Perpl
10 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity