pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,069,928
← previous block
next block →
recent activity
Analyzing
Block #71,069,928
11 transactions · 10 stateful · 2026-04-28 11:18:24 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,069,928
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
#5
setData
#6
updatePrices
· blocks 1
#7
updatePrices
· blocks 2
#8
updatePrices
· blocks 1
#10
updatePrices
#9
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w0
8
w1
9
w2
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x8fd63a…536c
6 touches
3 conflicts
0x00000000…0000
0x8fd63a…536c
6 touches
3 conflicts
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x01931e76…d502
0x34b655…2a6f
2 touches
0 conflicts
0x07934424…5b9c
0x34b655…2a6f
2 touches
0 conflicts
0x093b461e…1d71
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
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
3 conflicts on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity