← previous blocknext block →recent activity
Analyzing
Block #86,764,064
25 transactions · 20 stateful · 2026-07-10 04:10:47 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,764,064 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w19w212w314w015w122w423w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x008d197a…7a6d
0x34b655…2a6f
4 touches
1 conflict
0x41891af2…ed2a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity