pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,759,745
← previous block
next block →
recent activity
Analyzing
Block #94,759,745
9 transactions · 7 stateful · 2026-08-10 11:10:30 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,759,745
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xc95783…b2dd
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#6
updatePosition
#8
setData
#5
execFwdPositionOps
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6771eae2…7014
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x14b29ddb…0fd3
0x34b655…2a6f
4 touches
1 conflict
0xf3383813…4a0c
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x4e9b892b…6877
0x34b655…2a6f
2 touches
0 conflicts
0x62d6e82b…a750
0x34b655…2a6f
2 touches
0 conflicts
0x94ba9c4a…41d8
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
0x6771eae21e…6b7014
Audit this contract →
← previous block
·
next block →
recent activity