pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,528,432
← previous block
next block →
recent activity
Analyzing
Block #112,528,432
39 transactions · 32 stateful · 2026-10-11 17:29:19 UTC
Parallelism
82
/100
Blocked
47
%
Avg conflicts / tx
0.97
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,528,432
· 39 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
0x32d01e04
· blocks 2
#3
0x00040000
#4
0x000028ac
#5
postStateList
#6
0x5acec890
· blocks 7
#8
0x59558d29
#9
0xab083028
#11
0x5acec890
#12
0x5acec890
#13
0x928e4afa
#15
execOrders
#16
execPerpOps
#17
execPerpOps
#19
0x3f5c179b
#21
0x84403c1b
· blocks 1
#23
0x57368ddf
#24
execFwdPositionOpsV2
#25
setData
#26
0x61633731
#27
0x61d59c2d
· blocks 4
#36
0x0c7abd22
#37
0x0c7abd22
#38
0x0c7abd22
#2
0x32d01e04
· blocks 1
#7
0x5acec890
· blocks 6
#28
0x61d59c2d
· blocks 3
#10
0x5acec890
· blocks 2
#14
execOrders
· blocks 2
#18
0x0c7abd22
#29
0x61d59c2d
· blocks 2
#20
0x84403c1b
· blocks 1
#30
0x61d59c2d
· blocks 1
#32
execOrders
· blocks 3
#22
0x84403c1b
#31
0x61d59c2d
#33
execOrders
· blocks 2
#34
execOrders
· blocks 1
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
10
w2
14
w2
18
w2
20
w3
21
w0
22
w4
27
w0
28
w1
29
w2
30
w3
32
w3
33
w4
34
w5
35
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd23e9468…049a
0x508254…98bd
10 touches
10 conflicts
0x5086c64a…28ba
0x34b655…2a6f
10 touches
10 conflicts
0x451e482b…7e7d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3a663e9a…a9c6
0x508254…98bd
8 touches
6 conflicts
0x4ea2b33b…7dbc
0x508254…98bd
8 touches
6 conflicts
0x3a663e9a…a9c5
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9c4
0x508254…98bd
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:
0x508254c8…4a98bd
10 conflicts on slot
0xd23e9468e2…f4049a
Audit this contract →
← previous block
·
next block →
recent activity