pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,900,845
← previous block
next block →
recent activity
Analyzing
Block #87,900,845
10 transactions · 10 stateful · 2026-07-15 10:52:46 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,900,845
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#7
0x57368ddf
#8
setData
#9
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x147259c6…1709
0x34b655…2a6f
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xdb3774c5…2442
0x34b655…2a6f
4 touches
1 conflict
0x11ee3670…47f6
0x34b655…2a6f
2 touches
0 conflicts
0x17e1cbea…6bfb
0x34b655…2a6f
2 touches
0 conflicts
0x1ebe108b…72a0
0x34b655…2a6f
2 touches
0 conflicts
0x1f934561…e2bd
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
0x147259c661…b51709
Audit this contract →
← previous block
·
next block →
recent activity