pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,234,272
← previous block
next block →
recent activity
Analyzing
Block #94,234,272
9 transactions · 9 stateful · 2026-08-08 14:54:48 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,234,272
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
commit
#6
execFwdPositionOps
#7
setData
#8
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7ef0c17…df1d
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x3405ed3a…6ee6
0x34b655…2a6f
2 touches
0 conflicts
0xbb322930…ace5
0x34b655…2a6f
2 touches
0 conflicts
0xc8f39369…9e58
0x34b655…2a6f
2 touches
0 conflicts
0xccab8ea0…0a3a
0x34b655…2a6f
2 touches
0 conflicts
0xe8d58d34…426d
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
0xf7ef0c17cc…79df1d
Audit this contract →
← previous block
·
next block →
recent activity