pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,719,207
← previous block
next block →
recent activity
Analyzing
Block #90,719,207
10 transactions · 9 stateful · 2026-07-27 08:04:19 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,719,207
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
withdrawETH
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
0x29eed2d3
#7
0xc5a04723
#8
setData
#9
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab13117b…e40e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x258ee7d6…b664
0x57ea24…2cec
2 touches
0 conflicts
0x97d1efdc…77f3
0x57ea24…2cec
2 touches
0 conflicts
0xb2ceb102…9a4a
0x57ea24…2cec
2 touches
0 conflicts
0x2d360b55…d4f5
0x80f006…d585
2 touches
0 conflicts
0x2d360b55…d4f6
0x80f006…d585
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
0xab13117b19…94e40e
Audit this contract →
← previous block
·
next block →
recent activity