← previous blocknext block →recent activity
Analyzing
Block #86,910,247
20 transactions · 17 stateful · 2026-07-10 20:27:58 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,910,247 · 20 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
1w03w04w05w17w18w210w113w319w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb06917e8…6985
0x34b655…2a6f
6 touches
3 conflicts
0xc7a15219…7745
0xa6afd3…d132
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb0446875…2b96
0x34b655…2a6f
4 touches
1 conflict
0xf03bae24…db39
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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
3 conflicts on slot 0xb06917e887…5e6985
Audit this contract →
← previous block·next block →recent activity