pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,781,764
← previous block
next block →
recent activity
Analyzing
Block #86,781,764
9 transactions · 6 stateful · 2026-07-10 06:08:54 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,781,764
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
· blocks 2
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
setData
#7
0xd35ef3…61c0
#8
0x762599…6891
#2
0x5a5d9a99
· blocks 1
#3
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01a08f7d…dec6
0x34b655…2a6f
6 touches
3 conflicts
0x0253692b…cd47
0x34b655…2a6f
6 touches
3 conflicts
0x1209b0bb…87b4
0x34b655…2a6f
6 touches
3 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
6 touches
3 conflicts
0xdb3b7dab…f38a
0x34b655…2a6f
6 touches
3 conflicts
0xdc921364…4680
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 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
3 conflicts on slot
0x01a08f7dea…2ddec6
Audit this contract →
← previous block
·
next block →
recent activity