← previous blocknext block →recent activity
Analyzing
Block #87,517,884
21 transactions · 20 stateful · 2026-07-13 16:10:39 UTC
Parallelism
76/100
Blocked
55%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,517,884 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w18w211w112w214w315w417w218w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b580bf…f969
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x1d73754c…2e95
0x34b655…2a6f
6 touches
3 conflicts
0xa86351b8…2c5a
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x3c190da8…2a1b
0x34b655…2a6f
6 touches
3 conflicts
0xf1cc9519…84c1
0x34b655…2a6f
6 touches
3 conflicts
0x7fde2a18…a522
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 0x56b580bf44…22f969
Audit this contract →
← previous block·next block →recent activity