pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,491,873
← previous block
next block →
recent activity
Analyzing
Block #74,491,873
8 transactions · 7 stateful · 2026-05-14 07:30:10 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,491,873
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
swap
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6a057a7a
#6
setData
#7
0x39435dac
#3
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x056d63e5…1a7c
0x065c9d…c394
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x1f22f68e…76aa
0x34b655…2a6f
2 touches
0 conflicts
0x259f3523…e931
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
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
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity