pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,213,597
← previous block
next block →
recent activity
Analyzing
Block #72,213,597
10 transactions · 7 stateful · 2026-05-03 18:20:36 UTC
Parallelism
70
/100
Blocked
29
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,213,597
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#4
0x1a945f9c
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
0x558ca0…f2b6
#8
0x96cefd…ec32
#9
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…006f
0x1efe02…37d6
2 touches
0 conflicts
0x02cb4ffb…a3c3
0x1efe02…37d6
2 touches
0 conflicts
0x4bb230cd…4296
0x1efe02…37d6
2 touches
0 conflicts
0xa0aed947…28a5
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
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