pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,773,173
← previous block
next block →
recent activity
Analyzing
Block #90,773,173
37 transactions · 33 stateful · 2026-07-27 12:35:47 UTC
Parallelism
89
/100
Blocked
45
%
Avg conflicts / tx
0.65
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,773,173
· 37 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
execute_route
· blocks 2
#4
0x575c0012
#5
0x6a67511b
#6
0x6a67511a
#9
exactInputSingle
#10
0x6a67511a
#11
setData
#12
0xab083028
· blocks 2
#14
updatePrices
· blocks 1
#16
0x5a5d9a99
· blocks 3
#17
0x5a5d9a99
#18
0x5a5d9a99
#19
execFwdPositionOps
· blocks 3
#20
execFwdPositionOps
· blocks 1
#21
0x3f5c179b
#22
executeBatch
#30
execOrders
#32
0x59558d29
· blocks 2
#35
0xc7e3ec2c
#36
0xc7e3ec2c
#3
execute_route
· blocks 1
#7
execute
#13
0xab083028
· blocks 1
#15
updatePrices
#23
0x3f5c179b
#24
execFwdPositionOps
· blocks 1
#28
execOrders
· blocks 2
#33
0x59558d29
· blocks 1
#8
exactInputSingle
#25
execFwdPositionOps
· blocks 1
#26
0xed82b078
#29
execOrders
· blocks 1
#34
0x59558d29
#27
execOrders
#31
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
7
w1
8
w2
12
w0
13
w1
14
w0
15
w1
16
w0
19
w0
20
w0
23
w1
24
w1
25
w2
26
w2
27
w3
28
w1
29
w2
31
w3
32
w0
33
w1
34
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0xb1c78e35…21d3
0x34b655…2a6f
6 touches
3 conflicts
0xbc8801cc…2aef
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
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-MON/USDC
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity