pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,429,560
← previous block
next block →
recent activity
Analyzing
Block #74,429,560
12 transactions · 11 stateful · 2026-05-14 00:35:23 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,429,560
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
· blocks 1
#3
0x575c0012
#4
0xbbb036a8
#5
updatePrices
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
fulfillOrder
#9
0x6a051943
#10
setData
#11
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
0xd77e90ec…8c04
0x3bd359…433a
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e017
0x188d58…ea8e
2 touches
0 conflicts
0xcce2fd99…a8eb
0x3bd359…433a
2 touches
0 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
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