← previous blocknext block →recent activity
Analyzing
Block #87,132,609
17 transactions · 13 stateful · 2026-07-11 21:13:25 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,132,609 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w314w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26cdc92a…04ba
0x34b655…2a6f
8 touches
6 conflicts
0x4ab0fef9…caef
0x34b655…2a6f
6 touches
3 conflicts
0xdb88134d…d6c1
0x34b655…2a6f
6 touches
3 conflicts
0xdb88134d…d6c2
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe860e8c0…de9b
0x34b655…2a6f
6 touches
3 conflicts
0x619c81de…01b4
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
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 0x26cdc92a67…f604ba
Audit this contract →
← previous block·next block →recent activity