pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,882,695
← previous block
next block →
recent activity
Analyzing
Block #74,882,695
10 transactions · 9 stateful · 2026-05-16 03:04:07 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,882,695
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
redeemDelegations
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#7
0x5339c59f
#8
0x5339c59f
#9
0x6a07df1f
#2
updatePrices
#6
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x36b018…7610
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x8c47bf56…e4f6
0x065c9d…c394
2 touches
0 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
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:
0x36b018a2…e17610
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity