pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,288,783
← previous block
next block →
recent activity
Analyzing
Block #71,288,783
9 transactions · 8 stateful · 2026-04-29 11:35:19 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,288,783
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
collect
#2
forward
#3
updateDataFeedsValuesPartial
#4
setData
#5
updatePrices
· blocks 1
#6
updatePrices
· blocks 1
#7
updatePrices
#8
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x8fd63a…536c
4 touches
1 conflict
0x00000000…0001
0x8fd63a…536c
4 touches
1 conflict
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0xe18b8066…9f45
0x120151…c1d6
2 touches
0 conflicts
0x22882eec…bc8a
0x3bd359…433a
2 touches
0 conflicts
0x24092f07…3a01
0x3bd359…433a
2 touches
0 conflicts
0x2f1c865b…052a
0x3bd359…433a
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:
0x8fd63afb…2f536c
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity