pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,135,931
← previous block
next block →
recent activity
Analyzing
Block #93,135,931
10 transactions · 9 stateful · 2026-08-04 18:47:05 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,135,931
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 2
#6
executeBatch
#9
setData
#7
execFwdPositionOps
· blocks 1
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf394e6ad…f568
0x34b655…2a6f
4 touches
1 conflict
0x410c23da…5793
0x34b655…2a6f
4 touches
1 conflict
0x43e15ca4…039d
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x5ae70cdc…6411
0x34b655…2a6f
2 touches
0 conflicts
0x6a4e1e6a…254b
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity