pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,788,404
← previous block
next block →
recent activity
Analyzing
Block #90,788,404
33 transactions · 30 stateful · 2026-07-27 13:52:26 UTC
Parallelism
70
/100
Blocked
57
%
Avg conflicts / tx
1.39
Longest chain
10
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,788,404
· 33 txs across 10 waves · depth 10
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
#0
syscallReward
#1
0x67098489
#2
0x0c7abd22
#3
0xab083028
· blocks 3
#5
revealWithCallback
#6
execPerpOps
#7
execPerpOps
#8
0x6a676312
· blocks 1
#10
updatePrices
#11
0x5a5d9a99
· blocks 8
#15
updateDataFeedsValuesPartial
#16
approve
#19
0x62be7533
#25
execFwdPositionOps
#27
setData
#32
0x59558d29
#4
0xab083028
· blocks 2
#9
0x6a676312
#12
0x5a5d9a99
· blocks 6
#21
0x3f5c179b
· blocks 1
#13
0x5a5d9a99
· blocks 5
#17
execFwdPositionOps
· blocks 5
#20
0x3f5c179b
· blocks 1
#23
0xed82b078
#14
0x5a5d9a99
· blocks 2
#22
batchUpdate
#26
execOrders
· blocks 1
#18
execFwdPositionOps
· blocks 4
#24
execFwdPositionOps
· blocks 1
#28
execOrders
· blocks 3
#29
execOrders
· blocks 2
#30
execOrders
· blocks 1
#31
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w0
9
w1
11
w0
12
w1
13
w2
14
w3
17
w2
18
w4
20
w2
21
w1
22
w3
23
w2
24
w5
26
w3
28
w6
29
w7
30
w8
31
w9
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0dd44476…ef40
0x34b655…2a6f
8 touches
6 conflicts
0x1fbd24c7…325b
0x34b655…2a6f
8 touches
6 conflicts
0x538f77c2…a9e7
0xa6afd3…d132
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
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:
Perpl
10 conflicts on slot
0x6fe7d366be…a578ff
Audit this contract →
← previous block
·
next block →
recent activity