pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,385,300
← previous block
next block →
recent activity
Analyzing
Block #97,385,300
39 transactions · 32 stateful · 2026-08-19 16:00:19 UTC
Parallelism
82
/100
Blocked
63
%
Avg conflicts / tx
1.08
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,385,300
· 39 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
0x0c7abd22
· blocks 8
#3
0x0c7abd22
#6
0x0c7abd22
#7
0x0c7abd22
#8
0x0c7abd22
#10
0x0c7abd22
#12
matchOrders
#14
updatePrices
#16
updatePrices
#20
execOrder
· blocks 4
#25
execPerpOps
· blocks 1
#28
execOrders
· blocks 2
#31
handleOps
#32
0x3f5c179b
#35
execFwdPositionOpsV2
#36
setData
#37
0x4cb2db39
#38
0x59558d29
#2
0x0c7abd22
· blocks 3
#21
execOrder
· blocks 3
#22
execOrder
#26
execPerpOps
#4
0x0c7abd22
· blocks 2
#23
execOrder
· blocks 2
#5
0x0c7abd22
· blocks 5
#24
execOrder
#9
0x0c7abd22
· blocks 3
#11
0x41a8f47c
· blocks 2
#17
0xab083028
· blocks 3
#13
updatePrices
· blocks 1
#18
0x6ad2e98b
· blocks 1
#27
0x928e4afa
· blocks 1
#29
execOrders
· blocks 1
#33
0x3f5c179b
#15
updatePrices
#19
0xab083028
#30
execOrders
#34
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
5
w3
9
w4
11
w4
13
w5
15
w6
17
w4
18
w5
19
w6
27
w5
29
w5
34
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xe1c7da66…6c1b
0xd32edf…ff58
9 touches
10 conflicts
0x967ba723…6d0f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
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:
Kuru Exchange: MarginAccount
10 conflicts on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity