pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,344,343
← previous block
next block →
recent activity
Analyzing
Block #74,344,343
10 transactions · 8 stateful · 2026-05-13 15:08:16 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
#74,344,343
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
exactInputSingle
· blocks 1
#6
0x6a049458
#7
0xfd9d40…95e5
#8
approve
#9
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
0x3f1434d4…1ce1
0x3bd359…433a
4 touches
1 conflict
0x00000000…0003
0x2d59fc…cd50
4 touches
1 conflict
0x3f1434d4…1ce1
0x11ed3b…2c96
4 touches
1 conflict
0x456c8d76…7964
0x28c888…7777
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x93fdd2e2…d459
0x3bd359…433a
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