pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,909,736
← previous block
next block →
recent activity
Analyzing
Block #97,909,736
24 transactions · 22 stateful · 2026-08-21 12:39:18 UTC
Parallelism
79
/100
Blocked
64
%
Avg conflicts / tx
1.21
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,909,736
· 24 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x0c7abd22
· blocks 5
#3
updatePrices
· blocks 1
#4
execOrders
· blocks 1
#5
0x6ad2e98b
· blocks 3
#14
forward
#16
execFwdPositionOpsV2
#19
setData
#20
0x59558d29
#21
execOrders
#2
0x0c7abd22
· blocks 3
#6
0xab083028
· blocks 4
#22
execOrders
· blocks 1
#7
0xab083028
· blocks 3
#9
0x5acec890
· blocks 4
#23
execOrders
#8
0x41a8f47c
· blocks 1
#10
0x5acec890
· blocks 1
#13
0x3f5c179b
· blocks 1
#17
execFwdPositionOpsV2
· blocks 1
#11
0x5acec890
#12
0x3f5c179b
#15
0xed82b078
#18
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w0
5
w0
6
w1
7
w2
8
w3
9
w2
10
w3
11
w4
12
w4
13
w3
15
w4
17
w3
18
w4
22
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xf47b941b…b814
0xa6afd3…d132
6 touches
3 conflicts
0x305e45b5…fbdd
0xa6afd3…d132
6 touches
3 conflicts
0x3e598447…0e3f
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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:
Perpl
10 conflicts on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity