← previous blocknext block →recent activity
Analyzing
Block #87,870,105
21 transactions · 20 stateful · 2026-07-15 07:27:07 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,870,105 · 21 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
5w06w07w19w012w213w314w116w118w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c7e1952…d9c9
0x34b655…2a6f
10 touches
10 conflicts
0xa558e115…fc88
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x2385516f…eca5
0x34b655…2a6f
6 touches
3 conflicts
0x634549fe…c16b
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x3cb4257f…b98d
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
10 conflicts on slot 0x6c7e195218…27d9c9
Audit this contract →
← previous block·next block →recent activity