pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#71,330,809
← previous block
next block →
recent activity
Analyzing
Block #71,330,809
13 transactions · 12 stateful · 2026-04-29 16:15:25 UTC
Parallelism
77
/100
Blocked
17
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,330,809
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
addLiquidity
#4
handleOps
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x69f22f14
#9
setData
#10
updatePrices
· blocks 2
#11
updatePrices
· blocks 1
#12
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
12
w2
- 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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x59472e2a…be49
0x065c9d…c394
2 touches
0 conflicts
0x5c4e302e…6740
0x065c9d…c394
2 touches
0 conflicts
0x621b0cce…c801
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:
0x8fd63afb…2f536c
3 conflicts on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity