pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,609,020
← previous block
next block →
recent activity
Analyzing
Block #96,609,020
11 transactions · 8 stateful · 2026-08-16 22:28:14 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,609,020
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
#6
0x57368ddf
#7
execFwdPositionOpsV2
#8
setData
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89484dd9…3029
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3e950538…2259
0x34b655…2a6f
4 touches
1 conflict
0x7fb99184…e8bb
0x34b655…2a6f
4 touches
1 conflict
0x2d7ea048…d78e
0x34b655…2a6f
2 touches
0 conflicts
0x3727225e…a3cf
0x34b655…2a6f
2 touches
0 conflicts
0x4eb7ff25…1696
0x34b655…2a6f
2 touches
0 conflicts
0x68297b76…8e24
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
0x89484dd9d0…5e3029
Audit this contract →
← previous block
·
next block →
recent activity