pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,224,866
← previous block
next block →
recent activity
Analyzing
Block #72,224,866
12 transactions · 11 stateful · 2026-05-03 19:36:13 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,224,866
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
updatePrices
#3
0x9036287a
· blocks 1
#4
forward
#5
approve
#7
0x0c7abd22
#8
0x6df9e92b
#9
updateDataFeedsValuesPartial
#10
setData
#11
0x39435dac
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5f57db8c…0a4a
0x065c9d…c394
4 touches
1 conflict
0x10abe832…fd72
0x065c9d…c394
3 touches
1 conflict
0x39694186…40c4
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x55328e52…30b0
0x065c9d…c394
2 touches
0 conflicts
0xbdf98ce2…9107
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:
0x065c9d28…a9c394
1 conflict on slot
0x47b807a243…c53307
Audit this contract →
← previous block
·
next block →
recent activity