pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,351,513
← previous block
next block →
recent activity
Analyzing
Block #74,351,513
10 transactions · 8 stateful · 2026-05-13 15:55:53 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,351,513
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x21ee15…ba70
#4
0xd10227eb
#5
updatePrices
#6
updatePosition
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6decd77b…f8bf
0xd32edf…ff58
3 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
0x08073057…5069
0x065c9d…c394
2 touches
0 conflicts
0x153aba79…350b
0x065c9d…c394
2 touches
0 conflicts
0x29d35426…1ed4
0x065c9d…c394
2 touches
0 conflicts
0x3a829ffc…5102
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:
0xd32edf66…9fff58
1 conflict on slot
0x6decd77b3f…9bf8bf
Audit this contract →
← previous block
·
next block →
recent activity