pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,453,256
← previous block
next block →
recent activity
Analyzing
Block #98,453,256
37 transactions · 31 stateful · 2026-08-23 10:19:23 UTC
Parallelism
89
/100
Blocked
42
%
Avg conflicts / tx
0.51
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,453,256
· 37 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x6a8ac9a2
#2
exactInputSingle
#3
matchOrders
#4
setData
· blocks 1
#5
updatePrices
· blocks 1
#7
updatePrices
#8
execOrders
#9
execOrders
#10
0x6ad2e98b
#11
0xab083028
· blocks 2
#12
0x8263f5d9
#13
execOrders
· blocks 3
#15
updateDataFeedsValuesPartial
#16
0x59558d29
#17
0x59558d29
#18
execPerpOps
#19
execPerpOps
#21
0x5acec890
· blocks 3
#24
execFwdPositionOpsV2
#25
execFwdPositionOpsV2
· blocks 2
#27
redeemDelegations
#31
0xed82b078
#33
0x6a8ac9a2
#6
updatePrices
#14
execOrders
· blocks 1
#20
0x5acec890
#22
0x928e4afa
· blocks 1
#23
execFwdPositionOpsV2
· blocks 2
#26
execFwdPositionOpsV2
· blocks 1
#29
0x0c7abd22
· blocks 1
#34
setData
#28
execFwdPositionOpsV2
#30
execFwdPositionOpsV2
#32
0xed82b078
#35
execOrders
· blocks 1
#36
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
11
w0
13
w0
14
w1
20
w1
21
w0
22
w1
23
w1
25
w0
26
w1
28
w2
29
w1
30
w2
32
w2
34
w1
35
w2
36
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf3d7a307…4d63
0x065c9d…c394
6 touches
3 conflicts
0xfcfed5ae…c9ce
0x065c9d…c394
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x1a356d76…6c74
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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:
Kuru Exchange: Market-MON/USDC
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity