pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,271,840
← previous block
next block →
recent activity
Analyzing
Block #72,271,840
13 transactions · 9 stateful · 2026-05-04 00:51:58 UTC
Parallelism
85
/100
Blocked
22
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,271,840
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
exactInputSingle
#3
updatePrices
· blocks 1
#4
updatePrices
#6
updatePrices
#7
updatePrices
#8
updateDataFeedsValuesPartial
#9
0x3f5c179b
#10
0x6df9e92b
· blocks 1
#12
setData
#5
updatePrices
#11
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0x5e1b1a…7777
4 touches
1 conflict
0x4d1acd7c…f345
0x5e1b1a…7777
4 touches
1 conflict
0x00000000…0000
0x75c3ab…4f0d
4 touches
1 conflict
0x00000000…0001
0x75c3ab…4f0d
4 touches
1 conflict
0x5593214e…dfc1
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
2 touches
0 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:
0x5e1b1a14…587777
1 conflict on slot
0x44ad89ba62…49cf83
Audit this contract →
← previous block
·
next block →
recent activity