pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,852,179
← previous block
next block →
recent activity
Analyzing
Block #86,852,179
36 transactions · 27 stateful · 2026-07-10 13:59:35 UTC
Parallelism
83
/100
Blocked
44
%
Avg conflicts / tx
0.75
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,852,179
· 36 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x6a50fb3e
#2
matchOrders
#3
0xab083028
· blocks 2
#5
execPerpOps
#6
0x5a5d9a99
· blocks 4
#9
execFwdPositionOps
· blocks 4
#10
execFwdPositionOps
#11
0x3f5c179b
· blocks 2
#13
0x3f5c179b
#16
forward
#19
updateDataFeedsValuesPartial
#20
updateDataFeedsValuesPartial
#21
0x8bfde0…9486
#22
0x22fee2…5841
#23
0xc7de4e…47a2
#24
0xe4d2a5…7632
#25
setData
#26
0xfc2f7f…ef9a
#27
0x86855b…0a27
#28
0x930dd2…7df4
#31
execOrders
#34
0xc7e3ec2c
#35
0xc7e3ec2c
#4
0xab083028
#7
0x5a5d9a99
· blocks 2
#12
0x3f5c179b
#14
execFwdPositionOps
· blocks 3
#17
0xed82b078
· blocks 1
#8
0x5a5d9a99
· blocks 1
#15
execFwdPositionOps
· blocks 2
#18
0xed82b078
#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
4
w1
6
w0
7
w1
8
w2
9
w0
11
w0
12
w1
14
w1
15
w2
17
w1
18
w2
29
w2
30
w3
32
w4
33
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x2c390858…b1ed
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xac8a5059…fd42
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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:
Perpl
10 conflicts on slot
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity