pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,091,767
← previous block
next block →
recent activity
Analyzing
Block #88,091,767
34 transactions · 24 stateful · 2026-07-16 08:09:42 UTC
Parallelism
82
/100
Blocked
67
%
Avg conflicts / tx
1.06
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,091,767
· 34 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x6a58923e
#2
0x6a58923e
#3
0x6a58923e
#4
0xab083028
· blocks 4
#5
0xab083028
#6
0xab083028
#8
0xab083028
· blocks 1
#9
updatePrices
· blocks 4
#14
0x6a58923e
#15
0x5a5d9a99
· blocks 6
#18
execOrder
#23
0x3f5c179b
#27
execFwdPositionOps
#28
execFwdPositionOps
#29
updateDataFeedsValuesPartial
#30
0x6a58923e
#31
setData
#7
0xab083028
· blocks 3
#10
updatePrices
· blocks 3
#16
0x5a5d9a99
· blocks 2
#24
0x0c7abd22
#11
updatePrices
· blocks 2
#17
0x5a5d9a99
#19
execFwdPositionOps
· blocks 4
#22
0x3f5c179b
· blocks 2
#12
updatePrices
· blocks 1
#20
execFwdPositionOps
· blocks 2
#21
execFwdPositionOps
#25
0xed82b078
· blocks 1
#13
updatePrices
#26
0xed82b078
#32
execOrders
· blocks 1
#33
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
8
w0
9
w0
10
w1
11
w2
12
w3
13
w4
15
w0
16
w1
17
w2
19
w2
20
w3
22
w2
24
w1
25
w3
26
w4
32
w4
33
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0xa1ff0729…0146
0xa6afd3…d132
10 touches
10 conflicts
0x890a1db9…1712
0xa6afd3…d132
10 touches
10 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 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
10 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity