pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,625,525
← previous block
next block →
recent activity
Analyzing
Block #95,625,525
13 transactions · 11 stateful · 2026-08-13 11:59:42 UTC
Parallelism
77
/100
Blocked
18
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,625,525
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
transfer
#2
matchOrders
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
execFwdPositionOps
· blocks 2
#8
forward
#10
0x6a7db226
#11
deposit
#12
setData
#7
execFwdPositionOps
· blocks 1
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb632ec81…cf62
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2fa2d1bd…0221
0x34b655…2a6f
4 touches
1 conflict
0xa6311649…0132
0x34b655…2a6f
4 touches
1 conflict
0xaad1c5c0…ab91
0x754704…b603
2 touches
0 conflicts
0xdc255d21…c377
0x754704…b603
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
0xb632ec81a6…a2cf62
Audit this contract →
← previous block
·
next block →
recent activity