pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,977,623
← previous block
next block →
recent activity
Analyzing
Block #72,977,623
19 transactions · 16 stateful · 2026-05-07 07:15:36 UTC
Parallelism
37
/100
Blocked
75
%
Avg conflicts / tx
3.58
Longest chain
12
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,977,623
· 19 txs across 12 waves · depth 12
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
wave
w10
wave
w11
#0
syscallReward
#1
0x0c7abd22
· blocks 12
#13
execute_route
#15
execute
#16
0xeffdedb0
#17
setData
#18
0x8b23406f
#2
0x0c7abd22
· blocks 10
#3
0x0c7abd22
· blocks 9
#4
0x0c7abd22
· blocks 8
#5
0x0c7abd22
· blocks 7
#6
0x0c7abd22
· blocks 6
#7
0x0c7abd22
· blocks 6
#8
0x0c7abd22
· blocks 4
#14
execute_route
#9
0x0c7abd22
· blocks 3
#10
0x0c7abd22
· blocks 2
#11
0x0c7abd22
· blocks 1
#12
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
9
w8
10
w9
11
w10
12
w11
14
w7
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd16bfbd5…b07c
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
10 touches
10 conflicts
0x9ac040c1…8225
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 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
66 conflicts on slot
0xd16bfbd56d…b8b07c
Audit this contract →
← previous block
·
next block →
recent activity