pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,621,799
← previous block
next block →
recent activity
Analyzing
Block #83,621,799
33 transactions · 27 stateful · 2026-06-25 14:51:34 UTC
Parallelism
67
/100
Blocked
63
%
Avg conflicts / tx
1.42
Longest chain
11
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,621,799
· 33 txs across 11 waves · depth 11
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
wave
w10
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#3
0x6a3d40ed
· blocks 1
#4
0x6a3d40ed
#7
0xab083028
#10
0x6a3d40ed
#11
0x6a3d40ed
#12
0x6a3d40ed
#13
0x98717539
#14
0x5a5d9a99
· blocks 8
#21
updateDataFeedsValuesPartial
#22
updateDataFeedsValuesPartial
#24
execFwdPositionOps
#28
setData
#31
execOrders
#32
0xc7e3ec2c
#2
0x0c7abd22
· blocks 1
#5
0xab083028
· blocks 2
#9
0x6a3d40ed
#15
0x5a5d9a99
· blocks 5
#6
0xab083028
· blocks 1
#16
0x5a5d9a99
· blocks 4
#8
0xab083028
#17
0x5a5d9a99
· blocks 3
#18
0x98717539
· blocks 5
#19
0x98717539
· blocks 4
#20
0x98717539
· blocks 3
#23
execFwdPositionOps
· blocks 2
#25
execFwdPositionOps
· blocks 1
#26
execFwdPositionOps
· blocks 2
#27
execFwdPositionOps
#29
execOrders
· blocks 1
#30
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
5
w1
6
w2
8
w3
9
w1
14
w0
15
w1
16
w2
17
w3
18
w4
19
w5
20
w6
29
w9
30
w10
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xd2cdfa3f…f071
0x34b655…2a6f
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
6 touches
3 conflicts
0x8e739938…e7ab
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
0x34b655…2a6f
6 touches
3 conflicts
0xc2dcae88…f07a
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
21 conflicts on slot
0xe99d8e683a…2ea16e
Audit this contract →
← previous block
·
next block →
recent activity