pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,789,299
← previous block
next block →
recent activity
Analyzing
Block #75,789,299
10 transactions · 8 stateful · 2026-05-20 08:04:59 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
#75,789,299
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x0f6795d9
#3
transfer
· blocks 1
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a0d6ba3
#9
setData
#4
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0035
0xee8c0e…1242
4 touches
1 conflict
0x89a60880…86b2
0xee8c0e…1242
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x37801694…9efc
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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:
Wrapped Ether (WETH)
1 conflict on slot
0x0000000000…000035
Audit this contract →
← previous block
·
next block →
recent activity