pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,000,138
← previous block
next block →
recent activity
Analyzing
Block #99,000,138
38 transactions · 27 stateful · 2026-08-25 08:47:44 UTC
Parallelism
82
/100
Blocked
48
%
Avg conflicts / tx
0.76
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,000,138
· 38 txs across 7 waves · depth 7
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
#0
syscallReward
#1
0x0c7abd22
#2
0x0c7abd22
· blocks 3
#3
0x0c7abd22
#4
0x0c7abd22
#5
0x0c7abd22
#7
main_all
#8
0x5acec890
· blocks 3
#9
execOrders
#10
0xab083028
· blocks 3
#12
0x32d01e04
#13
0x8263f5d9
#16
execOrders
· blocks 2
#17
execOrder
#18
updateDataFeedsValuesPartial
#19
0x59558d29
#20
execPerpOps
#21
0x6cfade05
#22
execPerpOps
#27
0x3f5c179b
#30
execFwdPositionOpsV2
#31
transfer
#32
0x6a8d5727
#33
setData
#34
execOrders
#6
0x0c7abd22
· blocks 3
#15
0x5acec890
· blocks 3
#11
0xab083028
· blocks 1
#23
execFwdPositionOpsV2
· blocks 3
#25
0x0c7abd22
· blocks 1
#14
0xab083028
· blocks 1
#24
execFwdPositionOpsV2
· blocks 2
#26
0x0c7abd22
#28
execFwdPositionOpsV2
· blocks 1
#29
0xed82b078
#35
execOrders
· blocks 2
#36
execOrders
· blocks 1
#37
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
8
w0
10
w0
11
w2
14
w3
15
w1
16
w0
23
w2
24
w3
25
w2
26
w3
28
w3
29
w4
35
w4
36
w5
37
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0xf5e84574…a34c
0xd32edf…ff58
7 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf3981be5…2c47
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
6 conflicts on slot
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity