pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,629,415
← previous block
next block →
recent activity
Analyzing
Block #100,629,415
37 transactions · 29 stateful · 2026-08-31 01:51:40 UTC
Parallelism
81
/100
Blocked
45
%
Avg conflicts / tx
0.81
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,629,415
· 37 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
· blocks 7
#5
execute
#6
execute
#7
0xab083028
#8
0xab083028
#9
0x4ccf0801
· blocks 1
#10
updatePrices
#11
execOrders
#12
0x5acec890
· blocks 1
#16
0x928e4afa
#17
updateDataFeedsValuesPartial
#19
0x59558d29
#20
0x59558d29
#21
execPerpOps
#22
execPerpOps
#23
execOrders
#24
execOrders
· blocks 1
#26
setData
· blocks 1
#28
execFwdPositionOpsV2
· blocks 1
#30
handleOps
#31
0xc7068c7b
#32
0x61d59c2d
#33
execOrders
· blocks 3
#2
0x0c7abd22
· blocks 2
#18
0x59558d29
#25
execOrders
#27
setData
#29
execFwdPositionOpsV2
#3
0x0c7abd22
· blocks 4
#4
0x0c7abd22
#13
0x5acec890
· blocks 5
#14
0x5acec890
· blocks 1
#34
execOrders
· blocks 2
#15
0x5acec890
#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
2
w1
3
w2
4
w3
9
w0
12
w0
13
w3
14
w4
15
w5
18
w1
24
w0
25
w1
26
w0
27
w1
28
w0
29
w1
33
w0
34
w4
35
w5
36
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xac79a0c7…be16
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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