pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,501,064
← previous block
next block →
recent activity
Analyzing
Block #72,501,064
11 transactions · 9 stateful · 2026-05-05 02:20:20 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,501,064
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
#2
removeLiquidity
#3
0x0c7abd22
· blocks 1
#5
0x42bbae7a
#6
0x3f5c179b
#7
updateDataFeedsValuesPartial
#8
0x69f9545c
#9
0xbe70473d
#10
setData
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a2d53fd…a2d9
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x399cd013…b14f
0x23ae8c…7777
2 touches
0 conflicts
0xc5c465af…6afe
0x23ae8c…7777
2 touches
0 conflicts
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0xb4b3c404…f0aa
0x3bd359…433a
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:
0xd32edf66…9fff58
1 conflict on slot
0x9a2d53fdd8…cba2d9
Audit this contract →
← previous block
·
next block →
recent activity