pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,577,742
← previous block
next block →
recent activity
Analyzing
Block #87,577,742
11 transactions · 9 stateful · 2026-07-13 22:51:37 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,577,742
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
setData
#9
0xf985c4…352b
#10
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x435b08b5…d84e
0x34b655…2a6f
4 touches
1 conflict
0x16dd4651…e88f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa5391dd2…5129
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x17d11501…1364
0x34b655…2a6f
2 touches
0 conflicts
0x1927e608…bcc6
0x34b655…2a6f
2 touches
0 conflicts
0x27b9caf2…c102
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
0x435b08b54c…2bd84e
Audit this contract →
← previous block
·
next block →
recent activity