pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,239,180
← previous block
next block →
recent activity
Analyzing
Block #71,239,180
10 transactions · 10 stateful · 2026-04-29 06:05:12 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,239,180
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updatePrices
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
setData
#7
updatePrices
· blocks 1
#8
updatePrices
#2
0x0c7abd22
#9
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x6d43ee99…bdd6
0x1b6862…e19c
4 touches
1 conflict
0xa4e3b3b1…0911
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0xfafd791c…062a
0xa6afd3…d132
3 touches
1 conflict
0xbbb85d37…2252
0xd32edf…ff58
3 touches
1 conflict
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:
0x1b68626d…2de19c
1 conflict on slot
0x0000000000…000013
Audit this contract →
← previous block
·
next block →
recent activity