pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,228,885
← previous block
next block →
recent activity
Analyzing
Block #74,228,885
10 transactions · 8 stateful · 2026-05-13 02:20:26 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,228,885
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcf7468f4
#2
0x1094dc9f
· blocks 1
#3
0x0c7abd22
· blocks 1
#4
updateDataFeedsValuesPartial
#6
setData
#8
forward
#9
0x39435dac
#5
0x0c7abd22
#7
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
5
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xc0520614…9b55
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xf7bec652…fa1d
0x065c9d…c394
2 touches
0 conflicts
0xf823e97f…2ee6
0x065c9d…c394
2 touches
0 conflicts
0x194f2c02…19e6
0x2a68ba…90c5
2 touches
0 conflicts
0x968bdacb…f461
0x2a68ba…90c5
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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