pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,150,952
← previous block
next block →
recent activity
Analyzing
Block #101,150,952
39 transactions · 23 stateful · 2026-09-01 21:36:01 UTC
Parallelism
87
/100
Blocked
48
%
Avg conflicts / tx
0.41
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,150,952
· 39 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0xab083028
· blocks 3
#2
0x0c7abd22
#4
0x0c7abd22
#5
0xab083028
#6
0x8263f5d9
#7
0x8263f5d9
#8
0x8263f5d9
#9
0x8263f5d9
#10
0x8263f5d9
#11
0x8263f5d9
#13
execOrder
· blocks 3
#14
execOrder
· blocks 1
#17
0x59558d29
· blocks 1
#19
withdrawCommission
#20
0x0c7abd22
#21
0x0c7abd22
#22
0x0c7abd22
#23
0x0c7abd22
#24
0x0c7abd22
#25
0x0c7abd22
#26
0x0c7abd22
#27
0x0c7abd22
#28
setData
· blocks 1
#31
0x62be7533
#33
0x57368ddf
#34
forward
#36
0x6a9745b8
#3
0x4297b034
· blocks 1
#15
execOrder
· blocks 3
#18
0x59558d29
#29
setData
#32
0x3f5c179b
#12
0xab083028
#16
execOrder
#30
execFwdPositionOpsV2
· blocks 2
#35
execFwdPositionOpsV2
#37
execOrders
· blocks 1
#38
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
12
w2
13
w0
14
w0
15
w1
16
w2
17
w0
18
w1
28
w0
29
w1
30
w2
32
w1
35
w3
37
w3
38
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd9b50cd5…b4b1
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x4ca87477…f8da
0xa6afd3…d132
4 touches
1 conflict
0xb73d7959…fdb7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
3 conflicts on slot
0xaad6be10ae…2c0801
Audit this contract →
← previous block
·
next block →
recent activity