pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,876,180
← previous block
next block →
recent activity
Analyzing
Block #87,876,180
38 transactions · 27 stateful · 2026-07-15 08:07:45 UTC
Parallelism
79
/100
Blocked
48
%
Avg conflicts / tx
0.63
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,876,180
· 38 txs across 8 waves · depth 8
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
#0
syscallReward
#1
0x50a0b275
· blocks 4
#2
0x1094dc9f
#4
executePacked
#5
____MEV_X____Ga543
#6
0xcf7468f4
#7
0x0c7abd22
#8
execute
#9
main_all
#10
main_all
#12
updatePrices
#13
0x5a5d9a99
#14
0x5a5d9a99
· blocks 1
#15
updateDataFeedsValuesPartial
#20
0x3f5c179b
#23
0x3f5c179b
#24
0x3f5c179b
#26
batchUpdate
#29
0x6a574049
#30
0x16523d…b793
#31
0x536074…5871
#32
setData
#33
0x7db6ae…2c91
#36
0xc7e3ec2c
#37
0xc7e3ec2c
#3
____MEV_X____Ga543
· blocks 3
#16
execFwdPositionOps
· blocks 5
#22
updatePosition
#11
0xab083028
· blocks 3
#17
execFwdPositionOps
· blocks 3
#18
execFwdPositionOps
· blocks 2
#19
0x62be7533
#27
0xed82b078
#28
0xed82b078
#21
execFwdPositionOps
· blocks 1
#25
execFwdPositionOps
· blocks 1
#34
execOrders
· blocks 1
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
11
w2
14
w0
16
w1
17
w2
18
w3
19
w3
21
w4
22
w1
25
w5
27
w3
28
w3
34
w6
35
w7
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x3e0ef032…8627
0x34b655…2a6f
10 touches
10 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x5a36d0c8…12e3
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
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
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity