pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,654,906
← previous block
next block →
recent activity
Analyzing
Block #74,654,906
13 transactions · 12 stateful · 2026-05-15 01:43:24 UTC
Parallelism
31
/100
Blocked
67
%
Avg conflicts / tx
2.77
Longest chain
9
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,654,906
· 13 txs across 9 waves · depth 9
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
#0
syscallReward
#1
0xa96df62f
#2
updatePrices
· blocks 8
#11
updateDataFeedsValuesPartial
#12
setData
#3
updatePrices
· blocks 7
#4
updatePrices
· blocks 6
#5
updatePrices
· blocks 5
#6
updatePrices
· blocks 4
#7
updatePrices
· blocks 3
#8
updatePrices
· blocks 2
#9
updatePrices
· blocks 1
#10
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
6
w4
7
w5
8
w6
9
w7
10
w8
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
18 touches
36 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x69990b41…1968
0xd42a27…01c7
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
36 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity