pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,285,748
← previous block
next block →
recent activity
Analyzing
Block #72,285,748
21 transactions · 17 stateful · 2026-05-04 02:25:28 UTC
Parallelism
62
/100
Blocked
65
%
Avg conflicts / tx
0.95
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,285,748
· 21 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 5
#4
execute_route
#6
exactInputSingle
#7
0xe7be4706
#8
0xe7be4706
#10
0x98717539
· blocks 2
#12
updateDataFeedsValuesPartial
#15
setData
#16
0x55e58ed0
#2
0x0c7abd22
· blocks 3
#11
0x98717539
· blocks 1
#3
0x0c7abd22
· blocks 4
#18
createModule
#20
0x39435dac
#5
exactInputSingle
#9
0xe7be4706
· blocks 1
#13
0x0c7abd22
· blocks 1
#14
0x3f5c179b
· blocks 2
#17
0xed82b078
· blocks 1
#19
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w3
9
w3
10
w0
11
w1
13
w4
14
w5
17
w6
18
w2
19
w7
20
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x2ce2d49e…d185
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x6062b367…fef5
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 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:
0x1b68626d…2de19c
6 conflicts on slot
0x0000000000…000013
Audit this contract →
← previous block
·
next block →
recent activity