pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,668,325
← previous block
next block →
recent activity
Analyzing
Block #99,668,325
36 transactions · 28 stateful · 2026-08-27 17:04:14 UTC
Parallelism
67
/100
Blocked
57
%
Avg conflicts / tx
1.5
Longest chain
12
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,668,325
· 36 txs across 12 waves · depth 12
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
wave
w10
wave
w11
#0
syscallReward
#1
0x0c7abd22
· blocks 6
#4
0x0c7abd22
#6
0x0c7abd22
#9
0x6a906e86
· blocks 1
#11
0x5acec890
· blocks 2
#12
execOrders
#13
execOrders
#14
execOrders
#15
0x59558d29
#16
0x59558d29
#17
execPerpOps
#18
execOrders
#19
execFwdPositionOpsV2
· blocks 4
#20
0x3f5c179b
#21
0x3f5c179b
#22
0x3f5c179b
#27
setData
#28
0x61633731
#31
execOrders
#2
0x0c7abd22
· blocks 7
#10
0x6a906e86
#24
0xed82b078
#3
0x0c7abd22
· blocks 3
#5
0x0c7abd22
· blocks 5
#7
0x0c7abd22
· blocks 3
#8
0x0c7abd22
#23
execFwdPositionOpsV2
· blocks 7
#25
redeemDelegations
#26
execFwdPositionOpsV2
· blocks 1
#29
execOrders
· blocks 5
#30
execOrders
· blocks 4
#32
execOrders
· blocks 3
#33
execOrders
· blocks 2
#34
execOrders
· blocks 1
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w3
7
w4
8
w5
9
w0
10
w1
23
w5
24
w1
25
w6
26
w6
32
w8
34
w10
35
w11
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x05dda60a…00da
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x3af0dd8e…0025
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
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
15 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity