pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,930,116
← previous block
next block →
recent activity
Analyzing
Block #86,930,116
7 transactions · 5 stateful · 2026-07-10 22:40:39 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,930,116
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
0x3f5c179b
#4
execFwdPositionOps
#6
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe35b84bc…4d5b
0x34b655…2a6f
4 touches
1 conflict
0xa412324b…90ab
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb207488f…fca0
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xd1db601b…c70d
0x34b655…2a6f
4 touches
1 conflict
0x2de5f82a…e1d0
0x34b655…2a6f
4 touches
1 conflict
0x3be33cca…0fff
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
1 conflict on slot
0xe35b84bcc8…124d5b
Audit this contract →
← previous block
·
next block →
recent activity