pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,375,227
← previous block
next block →
recent activity
Analyzing
Block #73,375,227
15 transactions · 11 stateful · 2026-05-09 03:21:02 UTC
Parallelism
87
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,375,227
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
· blocks 1
#2
execute_route
#3
execute
#4
execute
#5
execute
#6
0x69fea895
#7
exactOutputSingle
#9
0x121eab2f
#10
updateDataFeedsValuesPartial
#11
0xe7be4706
#12
0x323fe4ce
#13
setData
#14
0x39435dac
#8
exactOutputSingle
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
2 touches
0 conflicts
0xa23619a7…40e4
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
0x9a55547719…9719a8
Audit this contract →
← previous block
·
next block →
recent activity