pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,751,119
← previous block
next block →
recent activity
Analyzing
Block #94,751,119
10 transactions · 9 stateful · 2026-08-10 10:26:51 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,751,119
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xbb1740dd
#2
0x5acec890
· blocks 3
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
setData
#5
execFwdPositionOps
· blocks 1
#6
execOrders
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3b1be…8122
0x34b655…2a6f
6 touches
3 conflicts
0x141a3ab6…f2cf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x5d88c95b…a508
0x065c9d…c394
2 touches
0 conflicts
0xfbad2c6c…0d32
0x188d58…ea8e
2 touches
0 conflicts
0xfbad2c6c…0d34
0x188d58…ea8e
2 touches
0 conflicts
0x0778475b…bd75
0x2a68ba…90c5
2 touches
0 conflicts
0x2a949bb2…8769
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
3 conflicts on slot
0xb5a3b1be7c…288122
Audit this contract →
← previous block
·
next block →
recent activity