pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,477,028
← previous block
next block →
recent activity
Analyzing
Block #99,477,028
33 transactions · 29 stateful · 2026-08-27 00:54:02 UTC
Parallelism
82
/100
Blocked
62
%
Avg conflicts / tx
0.94
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,477,028
· 33 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#2
0x6a8f8b22
#4
0x4ccf0801
· blocks 1
#5
0x6a8f8b22
#8
0x32d01e04
#9
execOrders
· blocks 1
#10
updatePrices
· blocks 2
#13
0x5acec890
· blocks 3
#17
0x59558d29
#18
0x59558d29
#19
updateDataFeedsValuesPartial
#20
execFwdPositionOpsV2
· blocks 4
#22
redeemDelegations
#28
setData
· blocks 1
#3
0xab083028
· blocks 4
#11
updatePrices
· blocks 1
#14
0x5acec890
· blocks 1
#16
0x4cb2db39
#21
execFwdPositionOpsV2
#23
execFwdPositionOpsV2
#29
setData
#30
execOrders
· blocks 2
#6
0xab083028
· blocks 1
#12
updatePrices
#15
0x5acec890
· blocks 2
#25
0xed82b078
· blocks 1
#7
0x6ad2e98b
· blocks 1
#26
0xed82b078
#27
execFwdPositionOpsV2
· blocks 2
#24
0x3f5c179b
#31
execOrders
· blocks 1
#32
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w0
6
w2
7
w3
9
w0
10
w0
11
w1
12
w2
13
w0
14
w1
15
w2
16
w1
20
w0
21
w1
23
w1
24
w4
25
w2
26
w3
27
w3
30
w1
31
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xea57afd0…4232
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