pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,055,017
← previous block
next block →
recent activity
Analyzing
Block #86,055,017
34 transactions · 29 stateful · 2026-07-06 21:12:05 UTC
Parallelism
88
/100
Blocked
55
%
Avg conflicts / tx
0.79
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,055,017
· 34 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x6a4c1a9d
· blocks 1
#4
0x6a4c1a9d
#5
0x6a4c1a9c
#6
0xab083028
· blocks 5
#10
updatePrices
· blocks 3
#14
updatePrices
#15
execOrders
· blocks 1
#17
updateDataFeedsValuesPartial
#18
updateDataFeedsValuesPartial
#19
execFwdPositionOps
· blocks 2
#20
execFwdPositionOps
#22
0x9e76c652
#27
0x6a4c1a9c
#28
setData
#30
execOrders
· blocks 2
#33
0xc7e3ec2c
#2
0x0c7abd22
· blocks 1
#7
0xab083028
· blocks 3
#11
updatePrices
· blocks 2
#16
execOrders
#23
0xed82b078
· blocks 1
#26
execFwdPositionOps
· blocks 1
#29
0x6a4c1a9d
#8
0xab083028
· blocks 2
#12
updatePrices
· blocks 1
#24
0xed82b078
#25
0xed82b078
#31
execOrders
· blocks 1
#9
0x6ad2e98b
#13
updatePrices
#21
0x3f5c179b
#32
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
6
w0
7
w1
8
w2
9
w3
10
w0
11
w1
12
w2
13
w3
15
w0
16
w1
19
w0
21
w3
23
w1
24
w2
25
w2
26
w1
29
w1
30
w0
31
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xa20a130c…5d59
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x76d1e78d…7877
0x40c49f…2af0
6 touches
3 conflicts
0x61377ba1…0bef
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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:
0x04fdeac2…f747d7
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity