pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,511,990
← previous block
next block →
recent activity
Analyzing
Block #96,511,990
12 transactions · 12 stateful · 2026-08-16 14:20:13 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,511,990
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
withdraw
#2
0x5acec890
#3
execFwdPositionOpsV2
· blocks 1
#5
setData
#6
execOrders
#7
execOrders
#8
execOrders
#9
execOrders
#10
execOrders
#11
execOrders
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaafc0c3d…64b6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08b4ef96…a666
0x1c8a33…d316
2 touches
0 conflicts
0x0efda1ec…23c5
0x1c8a33…d316
2 touches
0 conflicts
0xab94749e…6100
0x1c8a33…d316
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x344bc09a…942f
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
0xaafc0c3d1e…2464b6
Audit this contract →
← previous block
·
next block →
recent activity