pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,997,929
← previous block
next block →
recent activity
Analyzing
Block #98,997,929
36 transactions · 31 stateful · 2026-08-25 08:36:26 UTC
Parallelism
81
/100
Blocked
39
%
Avg conflicts / tx
0.75
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,997,929
· 36 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
execute
· blocks 2
#3
executePacked
#4
0x5acec890
· blocks 1
#5
execOrders
· blocks 3
#6
updateDataFeedsValuesPartial
#8
0x6a8d5482
#9
0x59558d29
#11
execPerpOps
· blocks 1
#13
0xe3a3c9cc
#14
0xa9b28aa6
#15
setData
#16
0x0c7abd22
#17
0x62be7533
#18
execFwdPositionOpsV2
· blocks 4
#20
0x3f5c179b
· blocks 1
#23
0x6a8d5481
#24
0xd7d660…0a12
#25
execOrders
· blocks 1
#26
execOrders
#28
execOrders
· blocks 1
#30
execOrders
#32
execOrders
#34
execOrders
· blocks 1
#2
0xaf5e395a
· blocks 1
#7
execOrders
#12
execPerpOps
#19
execFwdPositionOpsV2
· blocks 3
#21
batchUpdate
#27
execOrders
#10
0xb414539a
#22
execFwdPositionOpsV2
· blocks 2
#29
execOrders
· blocks 3
#31
execOrders
· blocks 2
#33
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
4
w0
5
w0
7
w1
10
w2
11
w0
12
w1
18
w0
19
w1
20
w0
21
w1
22
w2
25
w0
27
w1
28
w0
29
w3
31
w4
33
w5
35
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x248b95ac…c5d4
0x065c9d…c394
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
6 touches
3 conflicts
0xb409e204…89ac
0x34b655…2a6f
4 touches
1 conflict
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity