pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,454,379
← previous block
next block →
recent activity
Analyzing
Block #99,454,379
37 transactions · 26 stateful · 2026-08-26 23:00:01 UTC
Parallelism
73
/100
Blocked
54
%
Avg conflicts / tx
1.05
Longest chain
10
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,454,379
· 37 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
0xa9b28aa6
· blocks 3
#2
execute
#6
0xab083028
#7
0x32d01e04
#8
0x32d01e04
#9
0x8263f5d9
#10
updatePrices
#11
updatePrices
#12
0x6a8f7069
#13
0x59558d29
#14
0x41a8f47c
#15
0x41a8f47c
#16
execOrders
· blocks 4
#17
0x1ada0a83
#18
0x62be7533
#19
0x3f5c179b
#20
0x3f5c179b
· blocks 1
#23
forward
#24
execFwdPositionOpsV2
#26
execFwdPositionOpsV2
#28
setData
#29
0x6574c9…824d
#3
0xab083028
· blocks 3
#25
execFwdPositionOpsV2
· blocks 3
#4
0xab083028
· blocks 2
#27
execFwdPositionOpsV2
· blocks 1
#5
0xab083028
· blocks 1
#21
0x3f5c179b
#30
execOrders
· blocks 6
#22
0xed82b078
#31
execOrders
· blocks 5
#32
execOrders
· blocks 4
#33
execOrders
· blocks 3
#34
execOrders
· blocks 2
#35
execOrders
· blocks 1
#36
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w3
16
w0
20
w0
21
w3
22
w4
25
w1
27
w2
30
w3
31
w4
32
w5
33
w6
34
w7
35
w8
36
w9
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x065ff70b…356d
0x40c49f…2af0
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x886db264…846e
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
21 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity