pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,515,579
← previous block
next block →
recent activity
Analyzing
Block #74,515,579
15 transactions · 6 stateful · 2026-05-14 10:09:02 UTC
Parallelism
80
/100
Blocked
33
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,515,579
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#3
updatePrices
#4
updatePrices
#6
updatePrices
#7
0xed82b078
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x1a2ab6…9d32
#11
0xed64fd…71f6
#12
0xc03fde…27e0
#13
0xe8c670…a441
#14
0x39435dac
#2
updatePrices
· blocks 1
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x8d0e98f3…7ba0
0x34b655…2a6f
2 touches
0 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
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