pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,271,795
← previous block
next block →
recent activity
Analyzing
Block #72,271,795
12 transactions · 10 stateful · 2026-05-04 00:51:40 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,271,795
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
updatePrices
#4
0x69f7ee14
#5
0x9036287a
#6
0x98717539
· blocks 1
#8
updatePosition
#9
updateDataFeedsValuesPartial
#10
0x69f7ee13
#11
setData
#7
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8db1e0f2…2fcf
0x34b655…2a6f
4 touches
1 conflict
0x908d4442…2c4b
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0xe52133fd…b3a7
0x34b655…2a6f
4 touches
1 conflict
0xaef9058e…322a
0x34b655…2a6f
4 touches
1 conflict
0x1c913164…5c2e
0x34b655…2a6f
4 touches
1 conflict
0x49f231bb…c1c2
0x34b655…2a6f
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
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
1 conflict on slot
0x8db1e0f2ad…b02fcf
Audit this contract →
← previous block
·
next block →
recent activity