pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,344,909
← previous block
next block →
recent activity
Analyzing
Block #74,344,909
11 transactions · 9 stateful · 2026-05-13 15:12:01 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,344,909
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
exactInputSingle
· blocks 1
#6
0x366fe5db
#7
0x6a049539
#8
0x6a15ff…9081
#9
transfer
#10
setData
#5
exactInputSingle
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x2d59fc…cd50
4 touches
1 conflict
0x00000000…0003
0x2d59fc…cd50
4 touches
1 conflict
0x3f1434d4…1ce1
0x3bd359…433a
4 touches
1 conflict
0x3f1434d4…1ce1
0x11ed3b…2c96
4 touches
1 conflict
0x0fc41e7b…6831
0x98dc6e…8633
2 touches
0 conflicts
0x5b571ba0…f13a
0x98dc6e…8633
2 touches
0 conflicts
0x68faa0b9…14af
0x98dc6e…8633
2 touches
0 conflicts
0x7aada5bb…c8f0
0x98dc6e…8633
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:
0x2d59fc33…60cd50
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity