pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,684,916
← previous block
next block →
recent activity
Analyzing
Block #86,684,916
10 transactions · 8 stateful · 2026-07-09 19:22:09 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,684,916
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#2
updateDataFeedsValuesPartial
#3
0x9e76c652
#5
forward
#7
setData
#8
0xb8024e57
#9
execOrders
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xaba6578d…bd48
0x34b655…2a6f
4 touches
1 conflict
0xceb0f181…5b40
0x34b655…2a6f
4 touches
1 conflict
0x7eab4979…0d6c
0x34b655…2a6f
4 touches
1 conflict
0xf481b267…dc7d
0x34b655…2a6f
4 touches
1 conflict
0x7eab4979…0d6d
0x34b655…2a6f
4 touches
1 conflict
0xab4a9e70…a605
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
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity