pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,747,190
← previous block
next block →
recent activity
Analyzing
Block #95,747,190
10 transactions · 9 stateful · 2026-08-13 22:12:42 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,747,190
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
0x5acec890
· blocks 1
#4
0x5acec890
#6
forward
#7
setData
#8
setData
#9
execOrders
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0xfbff297c…19ff
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
2 touches
0 conflicts
0x1ac9f2ed…7be9
0x34b655…2a6f
2 touches
0 conflicts
0x77aa2f01…8939
0x34b655…2a6f
2 touches
0 conflicts
0x786935e3…44a9
0x34b655…2a6f
2 touches
0 conflicts
0x8a740d65…0429
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
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity