pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,479,041
← previous block
next block →
recent activity
Analyzing
Block #99,479,041
23 transactions · 21 stateful · 2026-08-27 01:04:10 UTC
Parallelism
70
/100
Blocked
67
%
Avg conflicts / tx
1.17
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,479,041
· 23 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 5
#2
0x0c7abd22
#6
0x8263f5d9
#8
updateDataFeedsValuesPartial
#10
execOrders
#13
0x59558d29
#19
setData
#20
execOrders
#3
0x0c7abd22
· blocks 6
#4
0x41a8f47c
· blocks 2
#5
0xab083028
· blocks 2
#9
0x928e4afa
#11
execOrder
· blocks 4
#15
0x0c7abd22
#7
0x8263f5d9
· blocks 1
#12
execOrder
· blocks 1
#14
execFwdPositionOpsV2
· blocks 3
#16
0x3f5c179b
#17
0x3f5c179b
#18
execFwdPositionOpsV2
· blocks 2
#21
execOrders
· blocks 1
#22
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w1
5
w2
7
w3
9
w2
11
w2
12
w3
14
w3
15
w2
16
w3
17
w4
18
w4
21
w5
22
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x8b7fe709…9d99
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd814f518…f5b4
0x34b655…2a6f
6 touches
3 conflicts
0x4ed3a10e…147a
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x7001f382…c3f2
0x34b655…2a6f
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:
Kuru Exchange: MarginAccount
6 conflicts on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity