pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,743,094
← previous block
next block →
recent activity
Analyzing
Block #71,743,094
16 transactions · 10 stateful · 2026-05-01 14:05:21 UTC
Parallelism
88
/100
Blocked
10
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,743,094
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x1094dc9f
#4
execute
#5
updateDataFeedsValuesPartial
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
0x98c01e2a
#10
0x5bf9264c
#11
0x5bf9264c
#12
0xeffdedb0
#13
0xeffdedb0
#14
setData
#15
forward
#3
0x9609049f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d0cb725…1c20
0x065c9d…c394
4 touches
1 conflict
0x968bdacb…f461
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c4
0x1b6862…e19c
2 touches
0 conflicts
0x4bef88e0…eaca
0x3bd359…433a
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:
0x065c9d28…a9c394
1 conflict on slot
0x7d0cb725cc…171c20
Audit this contract →
← previous block
·
next block →
recent activity