pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,100,281
← previous block
next block →
recent activity
Analyzing
Block #98,100,281
38 transactions · 31 stateful · 2026-08-22 04:42:49 UTC
Parallelism
84
/100
Blocked
58
%
Avg conflicts / tx
1.03
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,100,281
· 38 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 6
#2
0x0c7abd22
#5
0x7b84f330
· blocks 1
#6
main_all
#8
updatePrices
#9
updatePrices
#10
execOrders
· blocks 1
#11
0x6ad2e98b
· blocks 3
#13
0x32d01e04
· blocks 1
#17
execOrder
· blocks 3
#18
0x59558d29
#19
execOrders
· blocks 2
#20
execPerpOps
#21
execPerpOps
#22
0x30b5ce…6e6e
#30
placeBet
#33
setData
#34
0x1dc91e…400f
#35
execute
#3
0x0c7abd22
· blocks 5
#7
main_all
· blocks 1
#12
0xab083028
· blocks 2
#15
0x8263f5d9
· blocks 2
#36
execOrders
#37
0x7b84f330
#4
0x0c7abd22
· blocks 4
#14
0xab083028
· blocks 2
#28
0x3f5c179b
· blocks 1
#16
0xab083028
#23
0x5acec890
· blocks 2
#25
0x0c7abd22
· blocks 1
#31
0xed82b078
#32
0xed82b078
#24
0x5acec890
· blocks 2
#26
0x0c7abd22
#27
execFwdPositionOpsV2
#29
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w0
7
w1
10
w0
11
w0
12
w1
13
w0
14
w2
15
w1
16
w3
23
w3
24
w4
25
w3
26
w4
36
w1
37
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fff4bab…b178
0xd32edf…ff58
9 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x9ac040c1…8223
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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:
FastLane: FastLaneAuctionHandler
10 conflicts on slot
0x5fff4bab15…5db178
Audit this contract →
← previous block
·
next block →
recent activity