pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,584,281
← previous block
next block →
recent activity
Analyzing
Block #87,584,281
9 transactions · 6 stateful · 2026-07-13 23:35:22 UTC
Parallelism
78
/100
Blocked
33
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,584,281
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 2
#5
0x6a5576b2
#6
setData
#7
0xbccf74…16ec
#8
0x870bf5…617f
#3
execFwdPositionOps
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x0d2450be…7e0f
0x34b655…2a6f
4 touches
1 conflict
0x5d2f0b01…112a
0x34b655…2a6f
2 touches
0 conflicts
0x606bc50d…4c10
0x34b655…2a6f
2 touches
0 conflicts
0xb692c3d7…80d5
0x34b655…2a6f
2 touches
0 conflicts
0xbb0b83ab…defb
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
0x0733be30d6…38112f
Audit this contract →
← previous block
·
next block →
recent activity