pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#71,560,832
← previous block
next block →
recent activity
Analyzing
Block #71,560,832
12 transactions · 10 stateful · 2026-04-30 17:52:06 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
#71,560,832
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#2
updatePrices
#4
updatePrices
#5
0xeffdedb0
#6
setData
#7
updateDataFeedsValuesPartial
#8
0x0c7abd22
#9
forward
#10
0x69f3973d
#11
0x39435dac
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x4ed096a7…1c6c
0x34b655…2a6f
2 touches
0 conflicts
0x631b4113…baa9
0x34b655…2a6f
2 touches
0 conflicts
0xa4e03780…74b0
0x34b655…2a6f
2 touches
0 conflicts
0xd6aabe89…92f5
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:
0x7e9d3a8a…4f9fda
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity