pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,367,303
← previous block
next block →
recent activity
Analyzing
Block #105,367,303
36 transactions · 32 stateful · 2026-09-16 16:30:07 UTC
Parallelism
81
/100
Blocked
72
%
Avg conflicts / tx
1.28
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,367,303
· 36 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 7
#4
0x0c7abd22
#6
0x6aaac413
#7
0x6aaac413
#9
setData
· blocks 1
#10
updatePrices
· blocks 3
#19
execPerpOps
#20
execPerpOps
#23
execFwdPositionOpsV2
#26
forward
#29
transfer
#30
0x6aaac413
#2
0x0c7abd22
· blocks 6
#11
updatePrices
· blocks 2
#17
0x4cb2db39
#18
0x59558d29
#31
setData
#3
0x0c7abd22
· blocks 5
#12
updatePrices
· blocks 1
#15
0x5acec890
· blocks 3
#5
0x0c7abd22
· blocks 3
#13
updatePrices
#16
0x928e4afa
#21
execOrders
· blocks 3
#32
execOrders
· blocks 3
#8
0xab083028
· blocks 3
#22
execOrders
· blocks 1
#33
execOrders
· blocks 2
#14
0xab083028
#24
execFwdPositionOpsV2
· blocks 1
#27
0xed82b078
· blocks 1
#34
execOrders
· blocks 1
#25
execFwdPositionOpsV2
#28
0xed82b078
#35
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
w4
9
w0
14
w5
15
w2
16
w3
17
w1
18
w1
21
w3
22
w4
24
w5
25
w6
27
w5
28
w6
31
w1
32
w3
33
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x6d43ee99…bdd9
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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:
0xf5b5f7f8…a36d70
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity