pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,206,989
← previous block
next block →
recent activity
Analyzing
Block #99,206,989
35 transactions · 32 stateful · 2026-08-26 02:14:44 UTC
Parallelism
83
/100
Blocked
50
%
Avg conflicts / tx
0.86
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,206,989
· 35 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
execute_route
· blocks 1
#3
0x4ccf0801
· blocks 1
#4
0x6a8e4c8c
· blocks 1
#7
0xa96df62f
#8
updatePrices
· blocks 2
#11
0x5acec890
· blocks 3
#12
0xab083028
· blocks 1
#13
0xab083028
#15
0x0c7abd22
· blocks 3
#18
0x9572a5…fdc5
#19
execOrders
#21
0x59558d29
#22
execFwdPositionOpsV2
· blocks 1
#23
0x3f5c179b
#26
execOrders
#27
execFwdPositionOpsV2
#28
postStateList
#29
setData
#2
execute_route
· blocks 2
#5
0x6a8e4c8c
#9
updatePrices
· blocks 1
#14
execOrders
#20
0x4cb2db39
#25
0xed82b078
#30
execOrders
· blocks 4
#6
execute
· blocks 1
#10
updatePrices
#31
execOrders
· blocks 3
#16
0x0c7abd22
· blocks 2
#32
execOrders
· blocks 2
#17
0x0c7abd22
· blocks 1
#33
execOrders
· blocks 1
#24
0x0c7abd22
#34
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w0
5
w1
6
w2
8
w0
9
w1
10
w2
11
w0
12
w0
14
w1
15
w0
16
w3
17
w4
20
w1
22
w0
24
w5
25
w1
30
w1
31
w2
32
w3
33
w4
34
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xfc9ab126…9870
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0xfe20cb8f…f03d
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