pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,784,015
← previous block
next block →
recent activity
Analyzing
Block #90,784,015
8 transactions · 7 stateful · 2026-07-27 13:30:20 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,784,015
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a675de3
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
exactInputSingle
#6
setData
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xccb43802…7c7b
0x34b655…2a6f
4 touches
1 conflict
0x7032dc14…49ea
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x06c980ab…5577
0x34b655…2a6f
2 touches
0 conflicts
0x085e35d2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x085e35d2…8d20
0x34b655…2a6f
2 touches
0 conflicts
0x0cc5cf9a…310d
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
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity