← previous blocknext block →recent activity
Analyzing
Block #86,959,672
13 transactions · 13 stateful · 2026-07-11 01:58:09 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,959,672 · 13 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
2w03w16w08w19w210w312w4
- 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
0xb0446875…2b96
0x34b655…2a6f
6 touches
3 conflicts
0xe2b0d74d…949c
0xa6afd3…d132
4 touches
1 conflict
0x050376db…0f47
0x34b655…2a6f
4 touches
1 conflict
0x050376db…0f48
0x34b655…2a6f
4 touches
1 conflict
0xd17d2f92…1d4b
0x34b655…2a6f
4 touches
1 conflict
0xf2e22c06…42d6
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity