← previous blocknext block →recent activity
Analyzing
Block #87,787,084
25 transactions · 22 stateful · 2026-07-14 22:11:51 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,787,084 · 25 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
2w06w07w18w19w210w315w017w418w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x94bb14fe…8f47
0x34b655…2a6f
6 touches
3 conflicts
0x3fde350e…8d43
0x34b655…2a6f
6 touches
3 conflicts
0xfc4d32c0…39f9
0x34b655…2a6f
6 touches
3 conflicts
0x392cb73c…5150
0x34b655…2a6f
4 touches
1 conflict
0x4c08d72d…bdb9
0x34b655…2a6f
4 touches
1 conflict
0x587911c7…9e01
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity