← previous blocknext block →recent activity
Analyzing
Block #87,498,856
21 transactions · 18 stateful · 2026-07-13 14:03:14 UTC
Parallelism
57/100
Blocked
50%
Avg conflicts / tx
1.29
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,498,856 · 21 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
5w06w19w210w311w413w514w615w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x53f393fa…00b9
0x34b655…2a6f
10 touches
10 conflicts
0x6a4868a5…367e
0x34b655…2a6f
10 touches
10 conflicts
0x1274880c…3cdc
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x4bf44420…23ac
0x34b655…2a6f
4 touches
1 conflict
0x529f6617…f080
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity