← previous blocknext block →recent activity
Analyzing
Block #87,919,530
21 transactions · 20 stateful · 2026-07-15 12:57:43 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,919,530 · 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
4w05w16w07w112w213w315w418w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc3ac1732…1dbb
0x34b655…2a6f
6 touches
3 conflicts
0xd1952ceb…56be
0x34b655…2a6f
6 touches
3 conflicts
0x2e64e234…5cfa
0x34b655…2a6f
4 touches
1 conflict
0x2e92eb56…31c2
0x34b655…2a6f
4 touches
1 conflict
0x32422867…093b
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity