pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,070,102
← previous block
next block →
recent activity
Analyzing
Block #71,070,102
10 transactions · 9 stateful · 2026-04-28 11:19:34 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,070,102
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
· blocks 1
#2
exactInputSingle
#3
multicall
#5
updateDataFeedsValuesPartial
#6
0x6463ffd1
#8
setData
#9
0x39435dac
#4
0x55e58ed0
· blocks 1
#7
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0xcc77b33c…6e87
0x3bd359…433a
4 touches
1 conflict
0x00000000…000a
0x09f880…ede0
4 touches
1 conflict
0xd63729fb…c0ec
0x065c9d…c394
4 touches
1 conflict
0xdc7a27e1…d536
0x754704…b603
4 touches
1 conflict
0xe436ef16…99df
0x754704…b603
4 touches
1 conflict
0xfe49740d…4e57
0x754704…b603
4 touches
1 conflict
0x00000000…0007
0x09f880…ede0
4 touches
1 conflict
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x92d610a6f9…379a40
Audit this contract →
← previous block
·
next block →
recent activity