pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,673,718
← previous block
next block →
recent activity
Analyzing
Block #86,673,718
30 transactions · 27 stateful · 2026-07-09 18:07:23 UTC
Parallelism
73
/100
Blocked
67
%
Avg conflicts / tx
1.33
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,673,718
· 30 txs across 8 waves · depth 8
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#3
0x6a4fe3d3
· blocks 1
#6
0x5a5d9a99
· blocks 3
#11
execFwdPositionOps
· blocks 1
#12
updateDataFeedsValuesPartial
#13
0x3f5c179b
· blocks 2
#21
setData
#22
0x32366535
#23
0xda29c4…7393
#24
0xaf47a8bb
#29
0xc7e3ec2c
#2
0x0c7abd22
· blocks 7
#4
0x44ee09b1
#7
0x5a5d9a99
· blocks 3
#25
0x6a4fe3d3
#5
0xab083028
· blocks 5
#8
0x5a5d9a99
· blocks 1
#9
0x0c7abd22
#18
0xed82b078
#10
execFwdPositionOps
· blocks 3
#15
0xed82b078
· blocks 1
#14
execFwdPositionOps
· blocks 1
#16
0xed82b078
· blocks 3
#26
execOrders
· blocks 2
#17
0xed82b078
· blocks 2
#27
execOrders
· blocks 1
#19
0xed82b078
· blocks 1
#28
execOrders
#20
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
5
w2
6
w0
7
w1
8
w2
9
w2
10
w3
14
w4
15
w3
16
w4
17
w5
18
w2
19
w6
20
w7
25
w1
26
w4
27
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
6 touches
3 conflicts
0xfc578b53…9b1f
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xff196840…a453
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
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:
Kuru Exchange: MarginAccount
15 conflicts on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity