pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,510,802
← previous block
next block →
recent activity
Analyzing
Block #74,510,802
7 transactions · 7 stateful · 2026-05-14 09:36:54 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,510,802
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6a05982e
#3
setData
#4
swapExactIn
· blocks 1
#6
0x39435dac
#5
swapExactIn
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
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x1fd72ea6…d7dc
0x699abc…6a3b
4 touches
1 conflict
0xa9f89b80…ddad
0x699abc…6a3b
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x7170c140…36bc
0x34b655…2a6f
2 touches
0 conflicts
0x9e719c7a…df63
0x34b655…2a6f
2 touches
0 conflicts
0xac8e97a0…8426
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:
0x00000000…a9012a
1 conflict on slot
0x335a161d76…bdfe7f
Audit this contract →
← previous block
·
next block →
recent activity