pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,066,126
← previous block
next block →
recent activity
Analyzing
Block #71,066,126
8 transactions · 5 stateful · 2026-04-28 10:53:02 UTC
Parallelism
75
/100
Blocked
40
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,066,126
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
withdraw
#2
updateDataFeedsValuesPartial
#3
0x6463ffd1
· blocks 1
#5
setData
#6
updatePrices
· blocks 1
#4
0x0c7abd22
#7
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x179d145b…635a
0x065c9d…c394
2 touches
0 conflicts
0x2e95ca8a…7a12
0x065c9d…c394
2 touches
0 conflicts
0x420406d2…384b
0x065c9d…c394
2 touches
0 conflicts
0x496147ed…8fa0
0x065c9d…c394
2 touches
0 conflicts
0xa1becda9…a5c9
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:
0xc1a5781e…c78e1a
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity