pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,295,571
← previous block
next block →
recent activity
Analyzing
Block #74,295,571
11 transactions · 9 stateful · 2026-05-13 09:43:53 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,295,571
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
forward
#5
setData
#6
updatePriceFeedsIfNecessary
#7
0x5339c59f
#9
0x6a044851
#10
execute
#8
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x206bf3f7…6ef2
0x065c9d…c394
2 touches
0 conflicts
0x209d12c9…80e3
0x065c9d…c394
2 touches
0 conflicts
0x4d9b7180…722f
0x065c9d…c394
2 touches
0 conflicts
0x833fb060…b60c
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:
0x065c9d28…a9c394
1 conflict on slot
0xf823e97fa0…262ee6
Audit this contract →
← previous block
·
next block →
recent activity