pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,482,996
← previous block
next block →
recent activity
Analyzing
Block #90,482,996
11 transactions · 9 stateful · 2026-07-26 12:16:05 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,482,996
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
0x3f5c179b
· blocks 1
#6
forward
#7
execFwdPositionOps
#8
0x6a65fafc
#9
setData
#10
0x36326531
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x529e53cf…38e4
0xa6afd3…d132
4 touches
1 conflict
0x989252a1…d812
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00e2cc9a…61e3
0x34b655…2a6f
2 touches
0 conflicts
0x088adada…2aa2
0x34b655…2a6f
2 touches
0 conflicts
0x0ec74a3d…432f
0x34b655…2a6f
2 touches
0 conflicts
0x10f18761…8e0c
0x34b655…2a6f
2 touches
0 conflicts
0x16eb5040…a048
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0x529e53cf07…5438e4
Audit this contract →
← previous block
·
next block →
recent activity