pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,090,118
← previous block
next block →
recent activity
Analyzing
Block #71,090,118
14 transactions · 10 stateful · 2026-04-28 13:32:58 UTC
Parallelism
71
/100
Blocked
30
%
Avg conflicts / tx
0.43
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,090,118
· 14 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updatePrices
· blocks 3
#5
updatePrices
#6
updateDataFeedsValuesPartial
#7
updateTemporalNumericValuesV1
#8
0x69f0b782
#9
0x69f0b782
#10
setData
#11
0x39435dac
#12
updatePrices
#13
updatePrices
#2
updatePrices
· blocks 2
#3
updatePrices
· blocks 1
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xac206e47…ef7d
0x34b655…2a6f
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x1a6fae96…79e2
0xacc0a0…fd62
2 touches
0 conflicts
0x5250d39b…c3fb
0xacc0a0…fd62
2 touches
0 conflicts
0x65eebe63…9fa1
0xacc0a0…fd62
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:
0xb857c13a…1a9be1
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity