pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,591,052
← previous block
next block →
recent activity
Analyzing
Block #95,591,052
11 transactions · 11 stateful · 2026-08-13 09:06:18 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,591,052
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 2
#2
updateDataFeedsValuesPartial
#5
0x6a7d8982
#6
transfer
· blocks 1
#8
setData
#9
0x59558d29
#10
execOrders
#3
execFwdPositionOps
· blocks 1
#7
transfer
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x02fdb0e0…b418
0x34b655…2a6f
2 touches
0 conflicts
0x100593c2…32ce
0x34b655…2a6f
2 touches
0 conflicts
0x362894e6…669f
0x34b655…2a6f
2 touches
0 conflicts
0x362894e6…66a0
0x34b655…2a6f
2 touches
0 conflicts
0x40a9339c…6571
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
0x0a57a2b8cd…773cdd
Audit this contract →
← previous block
·
next block →
recent activity