← previous blocknext block →recent activity
Analyzing
Block #96,120,163
14 transactions · 14 stateful · 2026-08-15 05:29:08 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,120,163 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w29w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0xbb44cedd…c666
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x840175ed…af51
0x34b655…2a6f
6 touches
3 conflicts
0x7b481037…3457
0x34b655…2a6f
6 touches
3 conflicts
0x7ea60711…6098
0x34b655…2a6f
6 touches
3 conflicts
0x806b84e8…937f
0x34b655…2a6f
4 touches
1 conflict
0xa3c2f3db…ea7e
0x34b655…2a6f
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
3 conflicts on slot 0x7ee6007b44…92fd68
Audit this contract →
← previous block·next block →recent activity