pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,815,406
← previous block
next block →
recent activity
Analyzing
Block #86,815,406
8 transactions · 5 stateful · 2026-07-10 09:53:37 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,815,406
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x0f6795d9
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#6
updatePosition
#7
setData
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x808ff8b4…4450
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xdfc58aa8…e1df
0x34b655…2a6f
4 touches
1 conflict
0x09e78101…dad5
0x34b655…2a6f
2 touches
0 conflicts
0x0e5211d5…fbfe
0x34b655…2a6f
2 touches
0 conflicts
0x2096be10…a45a
0x34b655…2a6f
2 touches
0 conflicts
0x26054cbe…47df
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot
0x808ff8b47a…5b4450
Audit this contract →
← previous block
·
next block →
recent activity