pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,087,156
← previous block
next block →
recent activity
Analyzing
Block #95,087,156
34 transactions · 30 stateful · 2026-08-11 14:38:12 UTC
Parallelism
71
/100
Blocked
60
%
Avg conflicts / tx
1.29
Longest chain
10
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,087,156
· 34 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
0x6a7b344b
#2
0x6a7b344b
#3
0xab083028
· blocks 1
#4
0x0c7abd22
#6
execOrders
· blocks 4
#8
execOrder
· blocks 2
#13
execOrders
· blocks 1
#15
updateDataFeedsValuesPartial
#18
0x3f5c179b
#19
0x3f5c179b
· blocks 1
#21
0x30a19e01
#26
0x6a7b344b
#27
transfer
#28
setData
#31
execOrders
#5
0xab083028
· blocks 3
#7
execOrders
· blocks 3
#16
execFwdPositionOps
· blocks 1
#23
0xed82b078
· blocks 2
#9
0x5acec890
· blocks 6
#20
0x0c7abd22
· blocks 1
#24
0xed82b078
· blocks 1
#10
0x5acec890
· blocks 3
#17
execFwdPositionOps
· blocks 1
#25
0xed82b078
#11
0x5acec890
· blocks 5
#22
execFwdPositionOps
#12
0x5acec890
#14
execOrders
· blocks 3
#29
execOrders
· blocks 3
#30
execOrders
· blocks 2
#32
execOrders
· blocks 1
#33
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w0
7
w1
8
w0
9
w2
10
w3
11
w4
12
w5
14
w5
16
w1
17
w3
20
w2
22
w4
24
w2
25
w3
29
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x787cd73c…dd40
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
0x53f393fafd…2a00b9
Audit this contract →
← previous block
·
next block →
recent activity