pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,233,000
← previous block
next block →
recent activity
Analyzing
Block #72,233,000
7 transactions · 6 stateful · 2026-05-03 20:30:57 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,233,000
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePosition
#2
0x3f5c179b
#3
updateDataFeedsValuesPartial
#4
setData
· blocks 1
#6
0x39435dac
#5
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0xeedfbc…f7dc
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0xd1a0adf6…6e55
0x54cd53…9e7d
2 touches
0 conflicts
0x00268eba…56a3
0x6657d1…8ccc
2 touches
0 conflicts
0x08abfabe…4041
0x6657d1…8ccc
2 touches
0 conflicts
0x12ba4578…ce28
0x6657d1…8ccc
2 touches
0 conflicts
0x1fe06971…bfb8
0x6657d1…8ccc
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:
0xeedfbc36…f0f7dc
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity