pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,014,509
← previous block
next block →
recent activity
Analyzing
Block #96,014,509
10 transactions · 9 stateful · 2026-08-14 20:37:39 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,014,509
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
#5
0x222d4ad6
#6
0xed82b078
#7
batchUpdatePrice
#8
setData
#2
execOrders
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c7ed62f…76aa
0x34b655…2a6f
4 touches
1 conflict
0x4f97aa17…6776
0x34b655…2a6f
4 touches
1 conflict
0x852c17d3…f1a3
0x34b655…2a6f
4 touches
1 conflict
0xc751242c…efac
0x34b655…2a6f
4 touches
1 conflict
0x3c7c65d0…0b52
0x34b655…2a6f
2 touches
0 conflicts
0x48965dfe…432b
0x34b655…2a6f
2 touches
0 conflicts
0x4ab86fca…514d
0x34b655…2a6f
2 touches
0 conflicts
0x5f447bf3…57c7
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
0x8c7ed62f10…0576aa
Audit this contract →
← previous block
·
next block →
recent activity