pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,744,773
← previous block
next block →
recent activity
Analyzing
Block #75,744,773
9 transactions · 6 stateful · 2026-05-20 03:08:54 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,744,773
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
forward
#3
exactInputSingle
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x0f6795d9
#7
0x0f6795d9
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x26d0648a…db3a
0x065c9d…c394
2 touches
0 conflicts
0x8334a2b0…523b
0x065c9d…c394
2 touches
0 conflicts
0xc4106271…af81
0x065c9d…c394
2 touches
0 conflicts
0xc6ddb7cf…27f4
0x065c9d…c394
2 touches
0 conflicts
0xc8c191c4…57ac
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
0xdfa159d0ee…971576
Audit this contract →
← previous block
·
next block →
recent activity