pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,977,965
← previous block
next block →
recent activity
Analyzing
Block #72,977,965
24 transactions · 19 stateful · 2026-05-07 07:17:53 UTC
Parallelism
67
/100
Blocked
47
%
Avg conflicts / tx
1.25
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,977,965
· 24 txs across 8 waves · depth 8
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
#0
syscallReward
#1
0x0c7abd22
· blocks 7
#9
execute_route
#10
execute_route
#12
0xbbb036a8
#13
0x575c0012
#14
0x0756e95c
#15
0x719d975a
#16
0x69fc3d18
· blocks 1
#18
removeLiquidity
#19
updateDataFeedsValuesPartial
#20
removeLiquidity
#21
0xeffdedb0
#22
setData
#23
0x39435dac
#2
0x0c7abd22
· blocks 6
#17
0x69fc3d18
#3
0x0c7abd22
· blocks 6
#4
0x0c7abd22
· blocks 4
#11
execute_route
#5
0x0c7abd22
· blocks 3
#6
0x0c7abd22
· blocks 2
#7
0x0c7abd22
· blocks 1
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
5
w4
6
w5
7
w6
8
w7
11
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x510def4c…6966
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0xe4c6b0cb…0a25
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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
28 conflicts on slot
0x510def4cbf…9b6966
Audit this contract →
← previous block
·
next block →
recent activity