pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,575,811
← previous block
next block →
recent activity
Analyzing
Block #72,575,811
12 transactions · 8 stateful · 2026-05-05 10:38:03 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,575,811
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
0x3f5c179b
#9
0x69f9c902
#10
0xe9316489
#11
setData
#2
updatePrices
· blocks 1
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x51a814be…5a88
0x065c9d…c394
2 touches
0 conflicts
0x7cff799b…f024
0x065c9d…c394
2 touches
0 conflicts
0x8d41c226…1fe9
0x065c9d…c394
2 touches
0 conflicts
0x90c3f406…f754
0x065c9d…c394
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:
0x7e9d3a8a…4f9fda
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity