pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,330,255
← previous block
next block →
recent activity
Analyzing
Block #71,330,255
8 transactions · 8 stateful · 2026-04-29 16:11:43 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,330,255
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x69f22e36
#3
updatePriceFeedsIfNecessary
#4
0x98717539
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x278b8c29…a997
0x065c9d…c394
2 touches
0 conflicts
0x72d6e42e…9fe9
0x065c9d…c394
2 touches
0 conflicts
0xc54648f5…0e24
0x065c9d…c394
2 touches
0 conflicts
0xdf75e038…2ef8
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:
Perpl
1 conflict on slot
0x631b41138f…31baa9
Audit this contract →
← previous block
·
next block →
recent activity