pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,759,961
← previous block
next block →
recent activity
Analyzing
Block #74,759,961
13 transactions · 11 stateful · 2026-05-15 13:24:48 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,759,961
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
redeemDelegations
#6
setData
#7
forward
#8
0x39435dac
#9
commit
#10
cancelTournament
#11
approve
#12
exactInputSingle
#2
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d5aad2b…10c0
0xee77db…7777
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0988281e…11e0
0x34b655…2a6f
2 touches
0 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x5b26e38f…3654
0x34b655…2a6f
2 touches
0 conflicts
0x5cfec795…7c0e
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
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:
0xee77db33…a77777
1 conflict on slot
0x4d5aad2b70…7e10c0
Audit this contract →
← previous block
·
next block →
recent activity