pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,291,634
← previous block
next block →
recent activity
Analyzing
Block #96,291,634
11 transactions · 9 stateful · 2026-08-15 19:51:37 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,291,634
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
execPerpOps
#3
execPerpOps
#4
0x5acec890
· blocks 1
#5
updateDataFeedsValuesPartial
#7
setData
· blocks 1
#9
0xb2d4797b
#10
execOrders
#6
execFwdPositionOpsV2
#8
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xde231f36…1180
0x34b655…2a6f
4 touches
1 conflict
0x0a0d9257…eef6
0x34b655…2a6f
2 touches
0 conflicts
0x2a431ace…5f07
0x34b655…2a6f
2 touches
0 conflicts
0x53d9d925…f29b
0x34b655…2a6f
2 touches
0 conflicts
0x550b8900…a998
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…7212
0x34b655…2a6f
2 touches
0 conflicts
0xc824469a…641c
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity