← previous blocknext block →recent activity
Analyzing
Block #86,780,613
32 transactions · 23 stateful · 2026-07-10 06:01:13 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,780,613 · 32 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
2w06w18w010w012w113w014w116w218w019w120w221w329w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0xbbfc4dee…3243
0x065c9d…c394
5 touches
3 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
4 touches
1 conflict
0xf06c2cf5…61bd
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity