pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,266,624
← previous block
next block →
recent activity
Analyzing
Block #72,266,624
10 transactions · 9 stateful · 2026-05-04 00:16:55 UTC
Parallelism
80
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,266,624
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f7e5ef
· blocks 1
#3
updatePrices
· blocks 1
#5
0x9036287a
· blocks 1
#6
0x98717539
#7
updateDataFeedsValuesPartial
#9
setData
#2
0x69f7e5ef
#4
updatePrices
#8
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7b70e0ee…d8c6
0x065c9d…c394
2 touches
0 conflicts
0xbb8f7e8b…da57
0x065c9d…c394
2 touches
0 conflicts
0xbc14485a…1b0c
0x065c9d…c394
2 touches
0 conflicts
0xbda3d1ea…b927
0x065c9d…c394
2 touches
0 conflicts
0xd0098e5c…5b8d
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity