pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,787,121
← previous block
next block →
recent activity
Analyzing
Block #100,787,121
35 transactions · 29 stateful · 2026-08-31 15:05:07 UTC
Parallelism
74
/100
Blocked
55
%
Avg conflicts / tx
0.97
Longest chain
9
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,787,121
· 35 txs across 9 waves · depth 9
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
#0
syscallReward
#1
0x0c7abd22
· blocks 5
#4
0x4297b034
· blocks 2
#5
0x4297b034
#6
0x8263f5d9
#7
execOrders
#8
execOrder
· blocks 3
#9
execOrder
#10
0x59558d29
#11
0x59558d29
#13
execOrders
#14
batchRequestPriceCallback
#16
execFwdPositionOpsV2
#18
0x3f5c179b
#19
executeBatch
#21
0x57368ddf
#22
0xed82b078
#28
setData
#34
execOrders
#2
0x0c7abd22
· blocks 1
#12
execOrders
· blocks 3
#20
0x3f5c179b
· blocks 2
#3
0x0c7abd22
· blocks 1
#15
execFwdPositionOpsV2
· blocks 1
#23
execFwdPositionOpsV2
#25
0xed82b078
· blocks 1
#17
execFwdPositionOpsV2
· blocks 5
#26
0xed82b078
#27
0xed82b078
#24
execFwdPositionOpsV2
#29
execOrders
· blocks 4
#30
execOrders
· blocks 3
#31
execOrders
· blocks 2
#32
execOrders
· blocks 1
#33
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w0
8
w0
12
w1
15
w2
17
w3
20
w1
23
w2
24
w4
25
w2
26
w3
27
w3
29
w4
30
w5
31
w6
32
w7
33
w8
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x79347b24…9fba
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x0a6cb118…4ca5
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:
Perpl
10 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity