pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,698,295
← previous block
next block →
recent activity
Analyzing
Block #96,698,295
9 transactions · 8 stateful · 2026-08-17 05:57:14 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,698,295
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#7
0xed82b078
#8
setData
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2391abe…d635
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd5c98027…9fd9
0x34b655…2a6f
4 touches
1 conflict
0x748ce49f…a12c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x5906754f…b584
0x34b655…2a6f
2 touches
0 conflicts
0x6e9da12d…8459
0x34b655…2a6f
2 touches
0 conflicts
0xb3fb9fb5…64db
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
0xc2391abed2…7fd635
Audit this contract →
← previous block
·
next block →
recent activity