pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,231,503
← previous block
next block →
recent activity
Analyzing
Block #75,231,503
9 transactions · 7 stateful · 2026-05-17 17:53:45 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,231,503
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x62be7533
· blocks 2
#3
updatePriceFeedsIfNecessary
#4
updateDataFeedsValuesPartial
#7
setData
#8
swap
#5
0x5339c59f
#6
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x39be6df7…8cb0
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4bef88e0…eaca
0x3bd359…433a
2 touches
0 conflicts
0x690117b9…2820
0x3bd359…433a
2 touches
0 conflicts
0x8c6f8e19…63b9
0x754704…b603
2 touches
0 conflicts
0xa1087a5c…66c4
0x754704…b603
2 touches
0 conflicts
0xe73ea8be…45fd
0x754704…b603
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity