pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,283,826
← previous block
next block →
recent activity
Analyzing
Block #74,283,826
7 transactions · 5 stateful · 2026-05-13 08:25:41 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,283,826
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
updateDataFeedsValuesPartial
#3
setData
#4
withdraw
#5
swapExactIn
· blocks 1
#6
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x970647ff…e277
0x699abc…6a3b
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x9861869c…f6a4
0x699abc…6a3b
3 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…003d
0x699abc…6a3b
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x79dbd873…1c11
0x699abc…6a3b
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:
0x699abc15…c86a3b
1 conflict on slot
0x970647ff17…6fe277
Audit this contract →
← previous block
·
next block →
recent activity