pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,070,609
← previous block
next block →
recent activity
Analyzing
Block #71,070,609
22 transactions · 18 stateful · 2026-04-28 11:22:57 UTC
Parallelism
73
/100
Blocked
50
%
Avg conflicts / tx
1.05
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,070,609
· 22 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x0c7abd22
· blocks 6
#3
execute_route
· blocks 4
#5
0x575c0012
#6
0xbbb036a8
#7
execute
#8
0x69f09909
#11
updatePrices
#12
postStateList
#13
0x98717539
#19
updateDataFeedsValuesPartial
#20
updateDataFeedsValuesPartial
#21
setData
#2
0x0c7abd22
· blocks 4
#4
execute_route
· blocks 1
#10
0xcf7468f4
· blocks 2
#18
0x6463ffd1
#9
exactOutputSingle
#14
0x0c7abd22
· blocks 3
#15
0x0c7abd22
· blocks 2
#16
0x0c7abd22
· blocks 1
#17
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
9
w2
10
w1
14
w2
15
w3
16
w4
17
w5
18
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8ec3e37…06e0
0xd32edf…ff58
11 touches
15 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
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
15 conflicts on slot
0xb8ec3e3785…2806e0
Audit this contract →
← previous block
·
next block →
recent activity