pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,816,337
← previous block
next block →
recent activity
Analyzing
Block #94,816,337
11 transactions · 10 stateful · 2026-08-10 15:55:11 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,816,337
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
postStateList
#2
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#6
execFwdPositionOps
#7
executeBatch
#8
execFwdPositionOps
#9
setData
#10
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90a66fa7…9014
0x34b655…2a6f
4 touches
1 conflict
0x6459805c…615d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x03a6363b…ad2b
0x34b655…2a6f
2 touches
0 conflicts
0x0673e54d…dd73
0x34b655…2a6f
2 touches
0 conflicts
0x15c22181…1354
0x34b655…2a6f
2 touches
0 conflicts
0x19d43eda…7465
0x34b655…2a6f
2 touches
0 conflicts
0x2f3b486d…efda
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
0x90a66fa7d4…cf9014
Audit this contract →
← previous block
·
next block →
recent activity