pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,993,851
← previous block
next block →
recent activity
Analyzing
Block #72,993,851
15 transactions · 12 stateful · 2026-05-07 09:03:46 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,993,851
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
· blocks 1
#3
exec
#4
0x0c7abd22
#5
updateDataFeedsValuesPartial
#6
deposit
#7
forward
#8
0xed82b078
#9
0x69fc55ea
#10
0xeffdedb0
#11
setData
#12
0xd2a6bd…a242
#13
exactInputSingle
#14
0x39435dac
#2
execute_route
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08943ea2…ed03
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0003
0x0c65a0…0852
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0xcce2fd99…a8eb
0x3bd359…433a
2 touches
0 conflicts
0xd77e90ec…8c04
0x3bd359…433a
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)
1 conflict on slot
0x08943ea26c…67ed03
Audit this contract →
← previous block
·
next block →
recent activity