pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,668,239
← previous block
next block →
recent activity
Analyzing
Block #94,668,239
11 transactions · 8 stateful · 2026-08-10 03:28:46 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,668,239
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb2d4797b
#2
execPerpOps
#3
execPerpOps
#4
settlePredictions
#5
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
0x6a7945e6
#10
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x522340e8…e6df
0x34b655…2a6f
4 touches
1 conflict
0x77efb543…f7c2
0x34b655…2a6f
4 touches
1 conflict
0x77efb543…f7c3
0x34b655…2a6f
4 touches
1 conflict
0x1aa86f4e…1b5d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x351d3d6f…e375
0x34b655…2a6f
4 touches
1 conflict
0x46483cb1…e7ca
0x34b655…2a6f
4 touches
1 conflict
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity