pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,129,160
← previous block
next block →
recent activity
Analyzing
Block #96,129,160
11 transactions · 8 stateful · 2026-08-15 06:14:24 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,129,160
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
execOrder
· blocks 1
#4
execOrders
#5
0x5acec890
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
#9
batchUpdate
#10
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0x80a49a52…b8af
0x34b655…2a6f
3 touches
1 conflict
0x31dbb134…fe41
0x065c9d…c394
2 touches
0 conflicts
0x49942a7e…54d9
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x567f60d3…0238
0x065c9d…c394
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity