← previous blocknext block →recent activity
Analyzing
Block #86,906,917
23 transactions · 21 stateful · 2026-07-10 20:05:42 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,906,917 · 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
4w05w16w19w210w311w012w116w019w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x3093e806…bde2
0x34b655…2a6f
4 touches
1 conflict
0x3800d0ea…6168
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4b8b3363…6632
0x34b655…2a6f
4 touches
1 conflict
0x4b8b3363…6633
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 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity