pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,145,731
← previous block
next block →
recent activity
Analyzing
Block #96,145,731
9 transactions · 8 stateful · 2026-08-15 07:37:48 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,145,731
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
execOrders
· blocks 1
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
· blocks 2
#8
setData
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3c082c7…f032
0x34b655…2a6f
4 touches
1 conflict
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0xf7933c2f…d104
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x02fdb0e0…b418
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc5c1e1b0…7a90
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
0xe3c082c74d…15f032
Audit this contract →
← previous block
·
next block →
recent activity