pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,841,268
← previous block
next block →
recent activity
Analyzing
Block #94,841,268
10 transactions · 8 stateful · 2026-08-10 18:00:36 UTC
Parallelism
70
/100
Blocked
38
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,841,268
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
· blocks 3
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
0x6a7a123c
#9
setData
#2
execOrders
· blocks 1
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01a056f8…64e4
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xcd6caad2…792a
0x34b655…2a6f
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0x14d24073…cba7
0x34b655…2a6f
4 touches
1 conflict
0xcd6caad2…7929
0x34b655…2a6f
4 touches
1 conflict
0x2e1f5171…ad2d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
3 conflicts on slot
0x01a056f88f…9b64e4
Audit this contract →
← previous block
·
next block →
recent activity