pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,586,279
← previous block
next block →
recent activity
Analyzing
Block #74,586,279
14 transactions · 7 stateful · 2026-05-14 18:05:04 UTC
Parallelism
86
/100
Blocked
14
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,586,279
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe87e9c…21c4
#2
approve
· blocks 1
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
updateDataFeedsValuesPartial
#9
0xed82b078
#10
setData
#11
0x3285d0…a4d7
#12
0x3524a2…2d8d
#13
0x39435dac
#3
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad66f231…3c24
0x5df178…7777
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x2c492d…444e
2 touches
0 conflicts
0x00000000…0002
0x2c492d…444e
2 touches
0 conflicts
0x00000000…0003
0x2c492d…444e
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x83f3d320…fb59
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:
0x5df178c7…167777
1 conflict on slot
0xad66f23135…753c24
Audit this contract →
← previous block
·
next block →
recent activity