pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,973,392
← previous block
next block →
recent activity
Analyzing
Block #72,973,392
11 transactions · 10 stateful · 2026-05-07 06:47:23 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,973,392
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
· blocks 1
#2
0x1094dc9f
· blocks 2
#3
removeLiquidity
#4
0x0c7abd22
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#10
0xeffdedb0
#5
swap
· blocks 1
#9
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
5
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x27a56239…e20e
0x065c9d…c394
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0x46cb45de…a568
0x188d58…ea8e
4 touches
1 conflict
0x70b2f813…783c
0x2a68ba…90c5
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0005
0x0594c7…a3be
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:
USDC (USDC)
3 conflicts on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity