pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,664,942
← previous block
next block →
recent activity
Analyzing
Block #96,664,942
10 transactions · 9 stateful · 2026-08-17 03:09:30 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,664,942
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
· blocks 1
#3
execOrders
#4
execFwdPositionOpsV2
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#8
0xed82b078
#9
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2fa1675…4e07
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x177f744d…b7dd
0x34b655…2a6f
2 touches
0 conflicts
0x2a5bc5cd…0a17
0x34b655…2a6f
2 touches
0 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
2 touches
0 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
2 touches
0 conflicts
0x5cc7e5aa…8945
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
0xb2fa1675e0…3c4e07
Audit this contract →
← previous block
·
next block →
recent activity