pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,920,320
← previous block
next block →
recent activity
Analyzing
Block #74,920,320
11 transactions · 8 stateful · 2026-05-16 07:14:54 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,920,320
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
requestRedeem
#2
0x000000b2
#3
forward
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
redeemDelegations
#7
deposit
#8
setData
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97b0b2ee…4666
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13f49a53…d555
0x103222…7496
2 touches
0 conflicts
0x00000000…0000
0x16b726…0a0e
2 touches
0 conflicts
0x00000000…000b
0x24b8be…7f9e
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x07183925…5c95
0x34b655…2a6f
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:
0x34b6552d…112a6f
1 conflict on slot
0x97b0b2ee68…854666
Audit this contract →
← previous block
·
next block →
recent activity