pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,200,746
← previous block
next block →
recent activity
Analyzing
Block #73,200,746
8 transactions · 6 stateful · 2026-05-08 08:00:20 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,200,746
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#4
exactInputSingle
#5
updateDataFeedsValuesPartial
#6
0x69fd988c
#7
setData
#3
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a354a63…0515
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x57e8fcb0…7003
0x065c9d…c394
2 touches
0 conflicts
0x70548aa5…dba0
0x065c9d…c394
2 touches
0 conflicts
0x7f189cf6…afab
0x065c9d…c394
2 touches
0 conflicts
0xc426faf3…0c1c
0x065c9d…c394
2 touches
0 conflicts
0xf1566b26…4feb
0x065c9d…c394
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:
0x065c9d28…a9c394
1 conflict on slot
0x2a354a6333…480515
Audit this contract →
← previous block
·
next block →
recent activity