pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,797,018
← previous block
next block →
recent activity
Analyzing
Block #95,797,018
11 transactions · 9 stateful · 2026-08-14 02:23:17 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,797,018
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
0x5acec890
· blocks 1
#4
0x5acec890
#5
execOrders
#8
0xed82b078
#9
setData
#10
0x61d59c2d
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa07e7b13…7513
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x1c255c26…11dd
0x34b655…2a6f
2 touches
0 conflicts
0x217bd767…b79e
0x34b655…2a6f
2 touches
0 conflicts
0x25e65ccc…c735
0x34b655…2a6f
2 touches
0 conflicts
0x4b67fb18…a176
0x34b655…2a6f
2 touches
0 conflicts
0x5473b588…06f9
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
0xa07e7b13f3…e77513
Audit this contract →
← previous block
·
next block →
recent activity