← previous blocknext block →recent activity
Analyzing
Block #87,671,876
21 transactions · 18 stateful · 2026-07-14 09:20:55 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,671,876 · 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
1w06w07w010w011w114w215w316w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x11d629eb…bcd9
0x34b655…2a6f
6 touches
3 conflicts
0x02679875…8d2f
0x34b655…2a6f
6 touches
3 conflicts
0x5a36d0c8…12e2
0x34b655…2a6f
4 touches
1 conflict
0x5a36d0c8…12e3
0x34b655…2a6f
4 touches
1 conflict
0xdec5bfea…d17f
0xa6afd3…d132
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity