pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,673,548
← previous block
next block →
recent activity
Analyzing
Block #94,673,548
11 transactions · 10 stateful · 2026-08-10 03:55:28 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,673,548
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0xed82b078
#6
0xed82b078
#8
0x6a794c28
#9
setData
#10
0xc7e3ec2c
#2
0x5acec890
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bde9f7f…c070
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00f245ce…1e10
0x34b655…2a6f
2 touches
0 conflicts
0x031cd48c…fd30
0x34b655…2a6f
2 touches
0 conflicts
0x30c5329c…711c
0x34b655…2a6f
2 touches
0 conflicts
0x4392cbcd…6a92
0x34b655…2a6f
2 touches
0 conflicts
0x4ae3b148…7ed2
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0x1bde9f7fc9…34c070
Audit this contract →
← previous block
·
next block →
recent activity