← previous blocknext block →recent activity
Analyzing
Block #86,259,065
11 transactions · 10 stateful · 2026-07-07 19:54:13 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,259,065 · 11 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
1w02w14w26w37w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd800e635…b1d7
0x34b655…2a6f
6 touches
3 conflicts
0x7d57af1b…11a4
0x34b655…2a6f
4 touches
1 conflict
0x9537a090…612b
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x0efc210ee8…0e70ab
Audit this contract →
← previous block·next block →recent activity