pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,962,120
← previous block
next block →
recent activity
Analyzing
Block #92,962,120
8 transactions · 6 stateful · 2026-08-04 04:11:29 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,962,120
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOps
· blocks 2
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
setData
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf61165ef…adb9
0x34b655…2a6f
4 touches
1 conflict
0x004989aa…b35a
0x34b655…2a6f
4 touches
1 conflict
0x71a3fd70…4a5b
0x34b655…2a6f
4 touches
1 conflict
0xedf2c231…d5e4
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x042f38b8…2eb5
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity