pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,199,133
← previous block
next block →
recent activity
Analyzing
Block #85,199,133
10 transactions · 9 stateful · 2026-07-02 22:08:42 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,199,133
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 2
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
0xed82b078
#5
0x9600f3ed
#7
0x6a46e1e2
#8
setData
#6
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3149127f…19a9
0x34b655…2a6f
4 touches
1 conflict
0xd63e616b…a07d
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00c45c58…7df2
0x34b655…2a6f
2 touches
0 conflicts
0x06f0d2ab…dd75
0x34b655…2a6f
2 touches
0 conflicts
0x09ce76d1…b412
0x34b655…2a6f
2 touches
0 conflicts
0x1af777a9…b403
0x34b655…2a6f
2 touches
0 conflicts
0x1c483719…720b
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
0x3149127f74…a719a9
Audit this contract →
← previous block
·
next block →
recent activity