pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,510,467
← previous block
next block →
recent activity
Analyzing
Block #74,510,467
10 transactions · 8 stateful · 2026-05-14 09:34:36 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,510,467
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swapExactIn
· blocks 1
#2
approve
#4
updateDataFeedsValuesPartial
#5
0x6a0597a3
#6
setData
#7
0x39435dac
#8
0x39435dac
#9
0x39435dac
#3
0x0d484c28
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0f4dbcb…926a
0x754704…b603
4 touches
1 conflict
0xe069120c…952c
0x000000…012a
4 touches
1 conflict
0x00000000…0004
0x465a0b…3980
4 touches
1 conflict
0x00000000…0005
0x465a0b…3980
4 touches
1 conflict
0x3b56d5f7…d11b
0x465a0b…3980
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x8e80434a…a96d
0x0555e3…2b9c
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
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:
USDC (USDC)
1 conflict on slot
0xb0f4dbcbad…5c926a
Audit this contract →
← previous block
·
next block →
recent activity