pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,314,204
← previous block
next block →
recent activity
Analyzing
Block #93,314,204
34 transactions · 31 stateful · 2026-08-05 09:43:29 UTC
Parallelism
82
/100
Blocked
48
%
Avg conflicts / tx
0.88
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,314,204
· 34 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
execute_route
· blocks 1
#3
exactOutputSingle
#4
setData
· blocks 1
#5
0xab083028
· blocks 3
#8
0x0c7abd22
· blocks 2
#10
0x41a8f47c
#11
0x5acec890
· blocks 4
#12
0x5acec890
#15
0x5acec890
#18
redeemDelegations
#20
updateDataFeedsValuesPartial
#21
updateDataFeedsValuesPartial
#22
updateDataFeedsValuesPartial
#23
updateDataFeedsValuesPartial
#24
executeBatch
#26
0xed82b078
#31
0x59558d29
· blocks 1
#33
0xc7e3ec2c
#2
execute_route
#6
0x6ad2e98b
· blocks 2
#13
0x5acec890
· blocks 4
#17
execFwdPositionOps
#28
setData
#32
0x59558d29
#7
0xab083028
· blocks 3
#14
0x5acec890
· blocks 3
#9
0x0c7abd22
· blocks 1
#16
execFwdPositionOps
· blocks 3
#19
execFwdPositionOps
#25
0x0c7abd22
· blocks 1
#29
execOrders
· blocks 1
#27
0xed82b078
#30
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w0
6
w1
7
w2
8
w0
9
w3
11
w0
13
w1
14
w2
16
w3
17
w1
19
w4
25
w4
27
w5
28
w1
29
w4
30
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e0a934…5fc7
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xca841faa…486a
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
0xb4e0a934b9…435fc7
Audit this contract →
← previous block
·
next block →
recent activity