pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,674,720
← previous block
next block →
recent activity
Analyzing
Block #94,674,720
11 transactions · 10 stateful · 2026-08-10 04:01:22 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,674,720
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
exactInputSingle
#3
0x0f6795d9
· blocks 2
#6
0x57368ddf
#7
forward
#8
0x6a794d8a
#9
approve
#10
setData
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd99d25df…ecd8
0x34b655…2a6f
4 touches
1 conflict
0xf3383813…4a0c
0x34b655…2a6f
4 touches
1 conflict
0xfb31d278…9107
0x34b655…2a6f
4 touches
1 conflict
0x0eac7709…66c3
0x34b655…2a6f
4 touches
1 conflict
0x1d0a04dd…b892
0x34b655…2a6f
4 touches
1 conflict
0x40bc5adc…eda6
0x34b655…2a6f
4 touches
1 conflict
0x4cb81411…37f6
0x34b655…2a6f
4 touches
1 conflict
0x7d7ed9e4…4a59
0x34b655…2a6f
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
1 conflict on slot
0xd99d25dff0…d8ecd8
Audit this contract →
← previous block
·
next block →
recent activity