pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,328,861
← previous block
next block →
recent activity
Analyzing
Block #74,328,861
12 transactions · 9 stateful · 2026-05-13 13:25:19 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,328,861
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xed82b078
#2
updatePrices
· blocks 2
#5
updatePrices
#6
0x1a945f9c
#7
updateTemporalNumericValuesV1
#8
updateDataFeedsValuesPartial
#9
0x6a047c36
#10
setData
#11
0x39435dac
#3
updatePrices
· blocks 1
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x55292f01…e29c
0x1efe02…37d6
2 touches
0 conflicts
0x58a1ffb8…36a0
0xacc0a0…fd62
2 touches
0 conflicts
0x65eebe63…9fa1
0xacc0a0…fd62
2 touches
0 conflicts
0x6915e135…8d20
0xacc0a0…fd62
2 touches
0 conflicts
0xc3eddd9a…b94d
0xacc0a0…fd62
2 touches
0 conflicts
0xe5d597a6…9955
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:
0xab35264b…1cfa38
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity