pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,387,509
← previous block
next block →
recent activity
Analyzing
Block #91,387,509
9 transactions · 8 stateful · 2026-07-29 16:08:26 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,387,509
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
· blocks 1
#6
0x6a6a25f1
#7
setData
#5
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2452c070…4c2c
0x34b655…2a6f
4 touches
1 conflict
0x0227484c…b688
0x34b655…2a6f
2 touches
0 conflicts
0x0227484c…b689
0x34b655…2a6f
2 touches
0 conflicts
0x060e7dc6…43e9
0x34b655…2a6f
2 touches
0 conflicts
0x0ea46b1d…c9a4
0x34b655…2a6f
2 touches
0 conflicts
0x10fec71b…e12f
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity