pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,289,461
← previous block
next block →
recent activity
Analyzing
Block #71,289,461
23 transactions · 21 stateful · 2026-04-29 11:39:49 UTC
Parallelism
78
/100
Blocked
52
%
Avg conflicts / tx
1.04
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,289,461
· 23 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
execute_route
· blocks 2
#2
execute_route
#3
0x69f1ee7d
#4
postPriceList
#5
execute
#7
exactInputSingle
#9
updatePrices
#10
0x20601463
· blocks 2
#11
0x98717539
· blocks 5
#19
updateDataFeedsValuesPartial
#20
setData
#6
execute
· blocks 1
#12
0x98717539
· blocks 5
#16
0x0c7abd22
· blocks 2
#8
execute
#13
0x98717539
· blocks 4
#17
0x0c7abd22
· blocks 1
#14
0x98717539
· blocks 1
#18
0x0c7abd22
#21
0x39435dac
· blocks 1
#15
0x98717539
#22
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
8
w2
10
w0
11
w0
12
w1
13
w2
14
w3
15
w4
16
w1
17
w2
18
w3
21
w3
22
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x801a6e57…d85c
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ad
0x8d66a4…3095
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
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:
0x34b6552d…112a6f
10 conflicts on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity