pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,681,524
← previous block
next block →
recent activity
Analyzing
Block #75,681,524
10 transactions · 7 stateful · 2026-05-19 20:08:08 UTC
Parallelism
80
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,681,524
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x719d975a
· blocks 1
#3
0x0c7abd22
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#7
forward
#8
setData
#9
0x42dd8743
#2
0x76368669
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x431bdef7…c4ec
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xad436b12…f632
0x1111b3…4111
2 touches
0 conflicts
0xb3eae1cb…7249
0x1111b3…4111
2 touches
0 conflicts
0xe2e94dfa…5026
0x2a68ba…90c5
2 touches
0 conflicts
0xb7fefa89…54dc
0x754704…b603
2 touches
0 conflicts
0xffe004da…e2f4
0x754704…b603
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