← previous blocknext block →recent activity
Analyzing
Block #86,674,750
23 transactions · 17 stateful · 2026-07-09 18:14:17 UTC
Parallelism
83/100
Blocked
53%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,674,750 · 23 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
1w02w13w04w15w16w27w19w210w320w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5b7b846d…1b95
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x88a3f631…1e35
0x34b655…2a6f
4 touches
1 conflict
0x9dec05f8…2f38
0x34b655…2a6f
4 touches
1 conflict
0xa4c4b591…7f9f
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity