pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,701,101
← previous block
next block →
recent activity
Analyzing
Block #71,701,101
10 transactions · 8 stateful · 2026-05-01 09:25:39 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,701,101
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f4720a
#2
updatePrices
#3
0x9036287a
· blocks 1
#4
0xeffdedb0
#5
exactInputSingle
#7
updateDataFeedsValuesPartial
#8
0x69f4720a
#9
setData
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8a23666…5f87
0x065c9d…c394
4 touches
1 conflict
0x21415b47…a8b1
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6b4811b6…8d5a
0x065c9d…c394
3 touches
1 conflict
0xd0ce1430…b6a4
0x065c9d…c394
3 touches
1 conflict
0x03d3105e…ba5a
0x065c9d…c394
3 touches
1 conflict
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:
0x065c9d28…a9c394
1 conflict on slot
0xe8a236668a…145f87
Audit this contract →
← previous block
·
next block →
recent activity