pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,497,293
← previous block
next block →
recent activity
Analyzing
Block #98,497,293
41 transactions · 32 stateful · 2026-08-23 14:01:17 UTC
Parallelism
90
/100
Blocked
47
%
Avg conflicts / tx
0.66
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,497,293
· 41 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xdf921160
· blocks 4
#2
0x6a8afda5
· blocks 1
#4
0x6a8afda5
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
execOrders
· blocks 1
#10
0xab083028
· blocks 3
#13
0xab083028
#14
execOrder
· blocks 3
#16
0x59558d29
#17
0xb414539a
#18
0x5acec890
· blocks 3
#21
execFwdPositionOpsV2
#26
0x0c7abd22
#28
setData
· blocks 1
#30
execOrders
#31
execOrders
#32
execOrders
· blocks 1
#33
execOrders
#34
execOrders
#35
execOrders
#36
execOrders
#37
execOrders
#38
execOrders
#3
0x6a8afda5
#5
0xf78cb219
· blocks 3
#11
0x6ad2e98b
· blocks 1
#15
execOrder
· blocks 2
#19
0x928e4afa
#25
batchUpdate
#29
setData
#39
execOrders
· blocks 1
#12
0xab083028
· blocks 2
#20
execFwdPositionOpsV2
· blocks 1
#27
0xed82b078
#40
execOrders
#22
0x62be7533
#23
0x0c7abd22
#24
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
5
w1
9
w0
10
w0
11
w1
12
w2
14
w0
15
w1
18
w0
19
w1
20
w2
22
w3
23
w3
24
w3
25
w1
27
w2
28
w0
29
w1
39
w1
40
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x353c7a6e…e124
0x34b655…2a6f
6 touches
3 conflicts
0xbad68552…e6bf
0x34b655…2a6f
6 touches
3 conflicts
0xba0ba8b9…7663
0x065c9d…c394
5 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
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity