pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,088,904
← previous block
next block →
recent activity
Analyzing
Block #99,088,904
35 transactions · 32 stateful · 2026-08-25 16:20:30 UTC
Parallelism
71
/100
Blocked
50
%
Avg conflicts / tx
1.49
Longest chain
10
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,088,904
· 35 txs across 10 waves · depth 10
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
#0
syscallReward
#1
0x0c7abd22
· blocks 6
#4
0x0c7abd22
#6
matchOrders
#7
0xab083028
#8
0x32d01e04
· blocks 2
#9
execOrders
#10
execOrders
· blocks 3
#11
execOrder
· blocks 1
#12
0x59558d29
#13
0x6a8dc145
#14
updatePrices
#15
0x41a8f47c
#17
execFwdPositionOpsV2
#18
execFwdPositionOpsV2
#19
0x3f5c179b
#20
0x3f5c179b
#25
0xed82b078
#26
setData
#2
0x0c7abd22
· blocks 3
#16
execOrder
· blocks 4
#21
0x3f5c179b
· blocks 1
#23
execFwdPositionOpsV2
· blocks 2
#3
0x0c7abd22
· blocks 2
#22
batchUpdate
#27
execOrders
· blocks 7
#5
0x0c7abd22
#24
execOrders
#28
execOrders
· blocks 6
#29
execOrders
· blocks 5
#30
execOrders
· blocks 4
#31
execOrders
· blocks 3
#32
execOrders
· blocks 2
#33
execOrders
· blocks 1
#34
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w3
8
w0
10
w0
11
w0
16
w1
21
w1
22
w2
23
w1
24
w3
27
w2
28
w3
29
w4
30
w5
31
w6
32
w7
33
w8
34
w9
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x1045386d…cb86
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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:
Perpl
28 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity