← previous blocknext block →recent activity
Analyzing
Block #87,752,691
25 transactions · 23 stateful · 2026-07-14 18:21:46 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,752,691 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w011w112w215w216w317w422w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5deef6f…6c3f
0x34b655…2a6f
8 touches
6 conflicts
0x80df1435…af82
0x34b655…2a6f
6 touches
3 conflicts
0x9001f549…089d
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xa92c8763…6d7f
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 0xa5deef6f49…976c3f
Audit this contract →
← previous block·next block →recent activity