← previous blocknext block →recent activity
Analyzing
Block #87,733,450
18 transactions · 18 stateful · 2026-07-14 16:13:04 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,733,450 · 18 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
4w05w16w07w18w19w211w313w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x067c61b8…650f
0x34b655…2a6f
8 touches
6 conflicts
0xa55c4598…2988
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x1e56f6b6…5940
0x34b655…2a6f
4 touches
1 conflict
0x313d3d93…4aa2
0x34b655…2a6f
4 touches
1 conflict
0x4cdf55e1…0f2d
0x34b655…2a6f
4 touches
1 conflict
0x4f2fabb0…9b09
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
6 conflicts on slot 0x067c61b803…d7650f
Audit this contract →
← previous block·next block →recent activity