pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,043,250
← previous block
next block →
recent activity
Analyzing
Block #71,043,250
14 transactions · 13 stateful · 2026-04-28 08:20:45 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,043,250
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
· blocks 1
#3
0x98717539
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
forward
#8
createModule
#9
0x69f06e55
#10
setData
#11
0x39435dac
#12
updatePrices
#13
updatePrices
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x893cd52c…5766
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x8d66a4…3095
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x03482eed…23c8
0x34b655…2a6f
2 touches
0 conflicts
0x108394d8…4411
0x34b655…2a6f
2 touches
0 conflicts
0x1697794d…fd34
0x34b655…2a6f
2 touches
0 conflicts
0x1be18303…442a
0x34b655…2a6f
2 touches
0 conflicts
0x25de453d…9573
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:
Perpl
1 conflict on slot
0x893cd52ce3…495766
Audit this contract →
← previous block
·
next block →
recent activity