pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,604,738
← previous block
next block →
recent activity
Analyzing
Block #97,604,738
41 transactions · 26 stateful · 2026-08-20 10:44:30 UTC
Parallelism
88
/100
Blocked
42
%
Avg conflicts / tx
0.46
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,604,738
· 41 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
createModule
· blocks 3
#2
execute
#3
0x50a0b275
#4
0xb472ce…35af
#5
execute
#6
0x7b84f330
· blocks 1
#7
0x05ee6a22
#8
0x0c7abd22
#9
exactInputSingle
#10
execute
· blocks 1
#11
exactInputSingle
#13
0x05ee6a22
#15
multicall
#17
0x0c7abd22
#18
execOrders
· blocks 2
#23
updateDataFeedsValuesPartial
#24
0xbb1740dd
#25
0xe3a3c9cc
#26
0x41a8f47c
#27
0x0c7abd22
#28
0x0c7abd22
· blocks 1
#29
execFwdPositionOpsV2
#30
0x3f5c179b
#32
0x0c7abd22
#34
0xed82b078
#35
setData
#36
0x61d59c2d
#37
0x59558d29
#38
execOrders
#12
0x05ee6a22
· blocks 2
#19
execOrder
· blocks 3
#31
0x0c7abd22
· blocks 1
#40
0x7b84f330
#14
0x05ee6a22
· blocks 1
#20
execOrder
· blocks 3
#33
0xed82b078
#16
0xab083028
#21
execOrder
· blocks 1
#22
execOrder
#39
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w0
10
w0
12
w1
14
w2
16
w3
18
w0
19
w1
20
w2
21
w3
22
w3
28
w0
31
w1
33
w2
39
w4
40
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x214dc988…ba27
0x34b655…2a6f
8 touches
6 conflicts
0xf92ca902…34c3
0x065c9d…c394
6 touches
3 conflicts
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0x011fb8e3…054a
0x34b655…2a6f
4 touches
1 conflict
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: MarginAccount
6 conflicts on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity