pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,257,287
← previous block
next block →
recent activity
Analyzing
Block #99,257,287
38 transactions · 27 stateful · 2026-08-26 06:27:48 UTC
Parallelism
79
/100
Blocked
41
%
Avg conflicts / tx
0.58
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,257,287
· 38 txs across 8 waves · depth 8
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x41a8f47c
#3
0x41a8f47c
#4
execOrders
#6
0x8263f5d9
#7
execOrders
· blocks 2
#8
0x5acec890
· blocks 1
#10
execOrders
· blocks 3
#12
0x59558d29
#13
0x59558d29
#14
execPerpOps
#15
execPerpOps
#16
execPerpOps
#17
execPerpOps
#18
0xe3a3c9cc
#19
execOrder
#22
execFwdPositionOpsV2
· blocks 2
#24
execFwdPositionOpsV2
#25
0x3f5c179b
#26
0x3f5c179b
#27
updatePosition
#28
0x3f5c179b
· blocks 1
#31
setData
#32
setData
#33
execOrders
#34
execOrders
#5
0xab083028
#9
0x5acec890
· blocks 1
#11
execOrders
· blocks 2
#30
0xed82b078
#20
execFwdPositionOpsV2
· blocks 3
#21
execFwdPositionOpsV2
· blocks 1
#23
execFwdPositionOpsV2
· blocks 2
#29
execFwdPositionOpsV2
#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
1
w0
5
w1
7
w0
8
w0
9
w1
10
w0
11
w1
20
w2
21
w3
22
w0
23
w4
28
w0
29
w5
30
w1
35
w5
36
w6
37
w7
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xd88c0588…ecca
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
3 conflicts on slot
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity