pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,429,766
← previous block
next block →
recent activity
Analyzing
Block #91,429,766
12 transactions · 10 stateful · 2026-07-29 19:42:16 UTC
Parallelism
83
/100
Blocked
30
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,429,766
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updatePrices
#4
0x5a5d9a99
· blocks 3
#6
updateDataFeedsValuesPartial
#7
batchUpdate
#10
forward
#11
setData
#5
0x5a5d9a99
#8
execFwdPositionOps
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51f60b9d…653f
0x34b655…2a6f
4 touches
1 conflict
0x9e04a514…7824
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xbbeac3b7…c14b
0x34b655…2a6f
4 touches
1 conflict
0x38e39eef…50bd
0x34b655…2a6f
2 touches
0 conflicts
0x59052228…add7
0x34b655…2a6f
2 touches
0 conflicts
0x83762542…18ed
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
0x51f60b9da7…28653f
Audit this contract →
← previous block
·
next block →
recent activity