pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,609,455
← previous block
next block →
recent activity
Analyzing
Block #96,609,455
11 transactions · 8 stateful · 2026-08-16 22:30:26 UTC
Parallelism
73
/100
Blocked
38
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,609,455
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x80419567
#2
execPerpOps
#3
execPerpOps
#4
execOrders
· blocks 2
#5
execOrders
· blocks 1
#8
setData
#9
transfer
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e246445…9e0e
0x34b655…2a6f
6 touches
3 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0xd9512d97…be3d
0x34b655…2a6f
4 touches
1 conflict
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x344bc09a…942f
0x34b655…2a6f
2 touches
0 conflicts
0x58888587…bb8d
0x34b655…2a6f
2 touches
0 conflicts
0x59991669…58c6
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
3 conflicts on slot
0x0e2464459c…149e0e
Audit this contract →
← previous block
·
next block →
recent activity