pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,606,387
← previous block
next block →
recent activity
Analyzing
Block #99,606,387
33 transactions · 32 stateful · 2026-08-27 11:50:15 UTC
Parallelism
70
/100
Blocked
47
%
Avg conflicts / tx
1
Longest chain
10
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,606,387
· 33 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
0x6ad2e98b
· blocks 3
#4
0x6ad2e98b
#5
0xab083028
· blocks 1
#7
updatePrices
#8
0x5acec890
#9
execOrder
· blocks 2
#10
0x59558d29
· blocks 1
#12
0x0c7abd22
· blocks 3
#14
updateDataFeedsValuesPartial
#15
execFwdPositionOpsV2
· blocks 3
#17
executeBatch
#18
0x3f5c179b
#20
0x57368ddf
#21
forward
#22
execFwdPositionOpsV2
#26
0x6a9024ef
#27
setData
#2
0xab083028
· blocks 1
#6
0xab083028
#11
0x59558d29
#13
0x0c7abd22
· blocks 2
#19
0x3f5c179b
#3
0xab083028
#16
execFwdPositionOpsV2
· blocks 4
#23
execFwdPositionOpsV2
· blocks 2
#25
execFwdPositionOpsV2
#24
execFwdPositionOpsV2
· blocks 1
#28
execOrders
· blocks 4
#29
execOrders
· blocks 3
#30
execOrders
· blocks 2
#31
execOrders
· blocks 1
#32
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
w0
6
w1
9
w0
10
w0
11
w1
12
w0
13
w1
15
w0
16
w2
19
w1
23
w3
24
w4
25
w3
28
w5
29
w6
30
w7
31
w8
32
w9
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x3e49348b…9445
0x34b655…2a6f
6 touches
3 conflicts
0xe61a3df2…f763
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x969295c6…6d07
0x34b655…2a6f
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