pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,377,124
← previous block
next block →
recent activity
Analyzing
Block #74,377,124
10 transactions · 9 stateful · 2026-05-13 18:46:20 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,377,124
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x39abec6b
#4
exactInputSingle
· blocks 1
#6
0x39435dac
#7
transfer
#8
setData
#9
0x39435dac
#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
0x07d64d54…6bfc
0x2ab50b…5c41
2 touches
0 conflicts
0x0849cefc…6a65
0x2ab50b…5c41
2 touches
0 conflicts
0x08dab78a…08fb
0x2ab50b…5c41
2 touches
0 conflicts
0x0ca4d360…a141
0x2ab50b…5c41
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