pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,901,289
← previous block
next block →
recent activity
Analyzing
Block #87,901,289
11 transactions · 10 stateful · 2026-07-15 10:55:44 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,901,289
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
handleOps
#6
execFwdPositionOps
#7
0x6a5767a8
#8
setData
#9
execOrders
#10
claim
#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
0x757057f2…8eed
0x34b655…2a6f
4 touches
1 conflict
0x796c1a47…2bfb
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…153c
0x34b655…2a6f
4 touches
1 conflict
0xfd864cf1…e1a0
0x34b655…2a6f
4 touches
1 conflict
0x3093e806…bde2
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
1 conflict on slot
0x757057f277…678eed
Audit this contract →
← previous block
·
next block →
recent activity