pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,242,189
← previous block
next block →
recent activity
Analyzing
Block #99,242,189
40 transactions · 26 stateful · 2026-08-26 05:11:51 UTC
Parallelism
82
/100
Blocked
42
%
Avg conflicts / tx
0.55
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,242,189
· 40 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
0xf78cb219
#2
execute
#3
0xdf921160
#4
0x1ada0a83
· blocks 1
#5
execute
#6
executePacked
#7
0x05ee6a22
#8
0x05ee6a22
#9
0x6a8e760f
#10
execute
#11
updatePrices
#13
execOrders
#14
updateDataFeedsValuesPartial
#15
0x5acec890
· blocks 2
#18
execPerpOps
#19
execPerpOps
#20
execPerpOps
#21
0x938bf18e
#22
0x6cfade05
#23
execOrders
· blocks 4
#24
execPerpOps
#25
0xe3a3c9cc
#28
0x62be7533
#30
0x62be7533
#31
0x0c7abd22
#32
0x3f5c179b
#38
0xed82b078
#39
setData
#12
0xab083028
· blocks 3
#16
0x5acec890
· blocks 1
#27
execFwdPositionOpsV2
· blocks 3
#17
0x928e4afa
· blocks 2
#35
0xed82b078
· blocks 1
#37
0xed82b078
#26
execFwdPositionOpsV2
· blocks 2
#36
0xed82b078
#29
execFwdPositionOpsV2
· blocks 2
#33
execFwdPositionOpsV2
· blocks 1
#34
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
12
w1
15
w0
16
w1
17
w2
23
w0
26
w3
27
w1
29
w4
33
w5
34
w6
35
w2
36
w3
37
w2
- 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
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
6 touches
3 conflicts
0x2f063f2c…f799
0x34b655…2a6f
6 touches
3 conflicts
0x5c1b956d…14d3
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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