pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,133,815
← previous block
next block →
recent activity
Analyzing
Block #94,133,815
11 transactions · 8 stateful · 2026-08-08 06:25:39 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,133,815
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#4
settlePredictions
#5
execFwdPositionOps
· blocks 1
#6
executeBatch
#8
setData
#9
exactInputSingle
#7
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w0
7
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf0dd955…8679
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf4ca4a80…b15d
0x34b655…2a6f
4 touches
1 conflict
0x8252706a…7ca5
0x34b655…2a6f
4 touches
1 conflict
0x41c66186…229a
0x34b655…2a6f
4 touches
1 conflict
0x32287d4a…6699
0x34b655…2a6f
2 touches
0 conflicts
0x38d36864…2cb0
0x34b655…2a6f
2 touches
0 conflicts
0x410b84ab…1dbc
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
0xbf0dd955ca…ce8679
Audit this contract →
← previous block
·
next block →
recent activity