pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,915,576
← previous block
next block →
recent activity
Analyzing
Block #95,915,576
12 transactions · 11 stateful · 2026-08-14 12:19:54 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,915,576
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
depositV3
#2
withdraw
#3
execPerpOps
#4
execPerpOps
#5
execOrders
#6
execFwdPositionOpsV2
· blocks 1
#7
0x3f5c179b
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#11
setData
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb255781f…2ffb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x06844d83…2e2f
0x1c8a33…d316
2 touches
0 conflicts
0x2da4f662…bc0d
0x1c8a33…d316
2 touches
0 conflicts
0xab94749e…6100
0x1c8a33…d316
2 touches
0 conflicts
0x1088dfef…9fc2
0x34b655…2a6f
2 touches
0 conflicts
0x1f356c5d…bf12
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
0xb255781fba…5d2ffb
Audit this contract →
← previous block
·
next block →
recent activity