pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,492,621
← previous block
next block →
recent activity
Analyzing
Block #98,492,621
33 transactions · 29 stateful · 2026-08-23 13:37:47 UTC
Parallelism
79
/100
Blocked
52
%
Avg conflicts / tx
0.82
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,492,621
· 33 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
0x6a8af822
#2
0x6a8af822
#3
0x41a8f47c
#4
0x6a8af822
#5
setData
· blocks 1
#7
updatePrices
· blocks 2
#10
execOrders
· blocks 3
#12
0xab083028
· blocks 3
#13
updateDataFeedsValuesPartial
#14
execOrders
#15
0x59558d29
#16
0x59558d29
#17
0x5acec890
· blocks 1
#22
0x3f5c179b
#24
executeBatch
#25
batchUpdate
#29
updateTemporalNumericValuesV1
#6
setData
#8
updatePrices
· blocks 1
#11
execOrders
· blocks 2
#18
execFwdPositionOpsV2
· blocks 3
#23
0x0c7abd22
· blocks 2
#9
updatePrices
#19
execFwdPositionOpsV2
· blocks 3
#27
0xed82b078
· blocks 1
#20
execFwdPositionOpsV2
· blocks 1
#26
execFwdPositionOpsV2
· blocks 1
#28
0xed82b078
#21
execFwdPositionOpsV2
#30
execOrders
· blocks 2
#31
execOrders
· blocks 1
#32
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w0
8
w1
9
w2
10
w0
11
w1
12
w0
17
w0
18
w1
19
w2
20
w3
21
w4
23
w1
26
w3
27
w2
28
w3
30
w4
31
w5
32
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
6 touches
3 conflicts
0x41c56387…a8f6
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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: Market-MON/USDC
6 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity