pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,557,542
← previous block
next block →
recent activity
Analyzing
Block #71,557,542
11 transactions · 7 stateful · 2026-04-30 17:30:08 UTC
Parallelism
73
/100
Blocked
29
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,557,542
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x69f39217
· blocks 2
#3
0x69f39217
#4
updateDataFeedsValuesPartial
#5
updatePrices
#6
updatePrices
#7
updatePrices
#9
0xeffdedb0
#10
setData
#2
0x69f39218
· blocks 1
#8
0x69f39218
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x7e9d3a…9fda
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x09106a95…1467
0xeedfbc…f7dc
2 touches
0 conflicts
0xdbadf6b0…43b2
0xeedfbc…f7dc
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:
0x681e908b…e1ae09
3 conflicts on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity