pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,643,086
← previous block
next block →
recent activity
Analyzing
Block #71,643,086
13 transactions · 13 stateful · 2026-05-01 02:59:29 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,643,086
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x67098489
· blocks 1
#2
0x9036287a
#4
updatePrices
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0xeffdedb0
#9
setData
#10
updatePriceFeedsIfNecessary
#11
collect
#12
forward
#3
execute
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0x18a91a7e…53f8
0x065c9d…c394
2 touches
0 conflicts
0x4e26952d…692d
0x065c9d…c394
2 touches
0 conflicts
0x5cdc09d4…9d86
0x065c9d…c394
2 touches
0 conflicts
0x98cc5373…9a4a
0x065c9d…c394
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:
0x754704bc…afb603
1 conflict on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity