pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,291,492
← previous block
next block →
recent activity
Analyzing
Block #96,291,492
11 transactions · 10 stateful · 2026-08-15 19:50:55 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,291,492
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
execOrder
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
· blocks 1
#9
setData
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0xa77975dc…94c7
0x09475a…400f
2 touches
0 conflicts
0xc0240a50…d410
0x111111…db61
2 touches
0 conflicts
0xec3e20e7…e008
0x111111…db61
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
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
0x9fd372a13e…ada959
Audit this contract →
← previous block
·
next block →
recent activity