pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,703,629
← previous block
next block →
recent activity
Analyzing
Block #87,703,629
36 transactions · 29 stateful · 2026-07-14 12:53:22 UTC
Parallelism
75
/100
Blocked
48
%
Avg conflicts / tx
1.25
Longest chain
9
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,703,629
· 36 txs across 9 waves · depth 9
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
#0
syscallReward
#1
0xab083028
· blocks 1
#3
0xab083028
#4
updatePrices
#5
0x6a5631b9
#6
0x6a5631b9
#7
updatePrices
#8
updatePrices
#9
updatePrices
#10
updatePrices
#11
updatePrices
#12
0x5a5d9a99
· blocks 10
#23
updateDataFeedsValuesPartial
#24
updateDataFeedsValuesPartial
#25
0x3f5c179b
#29
forward
#30
setData
#31
0xb8024e53
#32
0xb8024e53
#33
execOrders
#34
0xc7e3ec2c
#35
0xc7e3ec2c
#2
0x6ad2e98b
· blocks 2
#13
0x5a5d9a99
· blocks 8
#14
0x5a5d9a99
· blocks 5
#26
0x3f5c179b
· blocks 1
#15
0x5a5d9a99
· blocks 5
#28
batchUpdate
#16
0x5a5d9a99
· blocks 3
#20
execFwdPositionOps
· blocks 3
#17
0x98717539
· blocks 3
#22
execFwdPositionOps
· blocks 1
#18
0x98717539
· blocks 2
#27
execFwdPositionOps
#19
0x98717539
· blocks 1
#21
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
12
w0
13
w1
14
w2
15
w3
16
w4
17
w5
18
w6
19
w7
20
w4
21
w8
22
w5
26
w2
27
w6
28
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x27a78688…b891
0x34b655…2a6f
8 touches
6 conflicts
0x4f51d069…d0b4
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x895c2891…d873
0x34b655…2a6f
6 touches
3 conflicts
0xbf68b5d2…0eba
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
28 conflicts on slot
0x6fe7d366be…a578ff
Audit this contract →
← previous block
·
next block →
recent activity