pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,125,415
← previous block
next block →
recent activity
Analyzing
Block #85,125,415
11 transactions · 9 stateful · 2026-07-02 13:57:30 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
#85,125,415
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0x3f5c179b
#7
closeBetting
#8
setData
#9
execOrders
#10
execOrders
#2
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x91ecf924…70d8
0x34b655…2a6f
4 touches
1 conflict
0x9f40a209…1193
0x34b655…2a6f
4 touches
1 conflict
0xbbd3d75d…09aa
0x34b655…2a6f
4 touches
1 conflict
0xe47478a3…a058
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x14928b69…b98f
0x34b655…2a6f
4 touches
1 conflict
0x4384dd01…4f99
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
0x8e5cc69035…0db06b
Audit this contract →
← previous block
·
next block →
recent activity