pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,093,215
← previous block
next block →
recent activity
Analyzing
Block #96,093,215
10 transactions · 7 stateful · 2026-08-15 03:13:36 UTC
Parallelism
70
/100
Blocked
29
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,093,215
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x41a8f47c
#2
setData
#3
execFwdPositionOpsV2
· blocks 2
#4
execFwdPositionOpsV2
#6
updateDataFeedsValuesPartial
#7
0x30a19e01
#9
execOrders
#5
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x0e7b9722…cd2a
0x34b655…2a6f
2 touches
0 conflicts
0x127a4390…8e60
0x34b655…2a6f
2 touches
0 conflicts
0x1e0bed33…2e09
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
3 conflicts on slot
0xb4e0a934b9…435fc7
Audit this contract →
← previous block
·
next block →
recent activity