pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,692,796
← previous block
next block →
recent activity
Analyzing
Block #97,692,796
35 transactions · 29 stateful · 2026-08-20 18:16:14 UTC
Parallelism
80
/100
Blocked
52
%
Avg conflicts / tx
1.17
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,692,796
· 35 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
0xa96df62f
#2
0x0756e95c
#3
0xcf7468f4
#4
0x0756e95c
· blocks 3
#5
0xe33905c2
#8
0x90d5d0bd
#9
setData
#10
0xab083028
· blocks 2
#11
execOrder
· blocks 2
#12
execOrder
· blocks 3
#13
execPerpOps
#14
execPerpOps
#15
0x5acec890
· blocks 5
#17
execOrder
#22
0x3f5c179b
· blocks 1
#24
0x3f5c179b
#25
0x57368ddf
#29
0x59558d29
#30
execOrders
#6
0x41a8f47c
· blocks 2
#16
0x5acec890
· blocks 4
#31
execOrders
· blocks 3
#7
0x41a8f47c
· blocks 1
#18
0x5acec890
· blocks 2
#19
execFwdPositionOpsV2
· blocks 3
#20
execFwdPositionOpsV2
· blocks 3
#21
execFwdPositionOpsV2
· blocks 2
#23
0x3f5c179b
· blocks 1
#26
execFwdPositionOpsV2
#27
0xed82b078
· blocks 1
#32
execOrders
· blocks 2
#28
0xed82b078
#33
execOrders
· blocks 1
#34
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w2
10
w0
11
w0
12
w0
15
w0
16
w1
18
w2
19
w2
20
w3
21
w3
23
w3
27
w4
31
w1
32
w4
33
w5
34
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a9e9bd1…5368
0x2a68ba…90c5
8 touches
6 conflicts
0x157b6348…8604
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x2d5b00e8…4dcd
0xa6afd3…d132
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
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:
Kuru Exchange: MarginAccount
6 conflicts on slot
0x2a9e9bd1e2…355368
Audit this contract →
← previous block
·
next block →
recent activity