← previous blocknext block →recent activity
Analyzing
Block #87,910,829
19 transactions · 18 stateful · 2026-07-15 11:59:32 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,910,829 · 19 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
3w06w17w28w39w412w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72880226…1435
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x274ac476…27fa
0x34b655…2a6f
6 touches
3 conflicts
0x6cdad76f…2bed
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x96bfa04d…d06b
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
6 conflicts on slot 0x7288022679…181435
Audit this contract →
← previous block·next block →recent activity